PODCAST 3: Partner Story with Shannon Mullins, MVP
Quick Summary
Shannon Mullins shares her 25‑year journey from Great Plains (GP) to Microsoft Dynamics 365 Business Central (BC)—from her first implementation as an end user to leading a BC consulting practice. We dig into common misconceptions, the real work behind migrations, why discovery matters, and the game‑changing impact of Power Platform. If you’re GP‑curious or mid‑migration, this episode is a practical, encouraging compass.
Top takeaways
GP ≠ BC. Treat BC as a new, modern, cloud product—don’t carry GP assumptions forward.
Discovery first. Map real processes, integrations, and customizations before scoping the project.
Reduce ISVs. Many GP add‑ons consolidate down to a handful of apps in BC, lowering cost & complexity.
Power Platform is a force multiplier. Workflow, integrations, and notifications without heavy dev.
Plan history intentionally. Be careful what you migrate into Microsoft tables—deleting isn’t easy later.
Misconceptions GP Customers Should Drop
1) “BC is just GP in the cloud.”
It’s not. BC has a NAV lineage, is fully cloud‑hosted, and is markedly smoother to use. Issues like hung batches and constant user resets are not the norm in BC.
2) “All my GP problems will follow me.”
With solid discovery and design, migration is a chance to simplify and improve.
3) “We can stay on GP forever.”
Microsoft’s direction is clear: begin planning the move. Getting on a roadmap now avoids crunch later.
“We routinely take customers from 18 GP apps down to 4–5 in BC. Cost and complexity go down—that’s a big win.”
What Makes BC a Game Changer
Excel‑like productivity: Edit‑in‑Excel, copy/paste, and list exports speed up mass changes without separate tools.
Power Platform integration: Power Automate triggers (e.g., Concur ➜ BC), approvals, onboarding flows, and connectors reduce or eliminate custom dev.
Cloud velocity: Auto‑updates with pre‑checks, and proactive code validation ahead of new releases.
“The combination of Power Platform + BC lets us automate real business workflows without a dev every time.”
Challenges & How to Overcome Them
Discovery gaps
Half‑done projects often hide missing integrations (“someone presses a button and data appears”). Do a structured discovery before quoting to surface dependencies, customizations, and process realities.
Cost concerns
Migrations aren’t “press‑a‑button” projects. Budget for services and change management. (When available, programs like bridge‑to‑cloud licensing can help offset some costs.)
Change management
Expect a learning curve. Adoption improves when users see: “Here’s how you did it in GP — here’s the equivalent in BC.”
Training artifacts
Create visual, step‑by‑step guides (OneNote, screenshots) that show exactly which button to click and where.
Data Migration: Be Deliberate
Shannon’s team often avoids Microsoft’s migration tools for full history when doing chart‑of‑accounts (COA) clean‑ups or master data redesign. Instead, they:
Redesign COA segments and master data first (vendors/customers) so BC starts clean.
Load GP history into dedicated “history” tables (AP/AR/Bank/Inventory) for lookup/filtering—without polluting BC posting tables.
Consider hybrid access to GP history (e.g., Popdock) or retain a read‑only GP archive in the cloud.
Why it matters: Once history is in BC’s Microsoft tables, bulk deletion/combining is limited. Think twice, plan once.
If You’re Nervous About Change
“Implementations can feel like childbirth—painful until you reach the other end, then you’re glad you did it.”
Tips:
Focus on making users’ jobs easier (fewer steps, better visibility, automation). Adoption follows value.
Teach with side‑by‑side GP → BC mappings for each role/task.
Provide visual, click‑by‑click guides users can follow after training.
What Shannon Would Improve in BC
Role‑based permission sets: Better out‑of‑the‑box templates for CFO, Accounting Manager, AP/AR Clerk, etc.
Financial reporting: Continued improvements for scheduling, exporting, and distribution—alongside the new out‑of‑box Power BI reports.
For Consultants & Aspiring BC Pros
Get certified: Start with MB‑800. Hands‑on practice makes the exam far more intuitive.
Build repetitions: The first few implementations are the hardest—experience compounds.
Leverage programs: Microsoft’s ReSkill and Cross‑Skill initiatives help new and GP‑seasoned pros pivot into BC.
Find mentors & stick around: Don’t just job‑hop—learn under great leaders long enough to absorb breadth and depth.
Beyond the Keyboard: Shannon’s Reset Rituals
Travel. Skiing in winter. White‑water rafting in summer. Multi‑day trips into nature to recharge and come back sharper for clients.
Event Spotlight: Summit North America
Session: 30 Tips & Tricks to Becoming a BC Super User (with Kim Dallefeld)
When: Monday, October 20, 9:45 AM
Why it’s timely: Many GP power users are stepping into BC “accidental admin” roles. This session equips you to stabilize, secure, and scale.
Favorite Quotes
“Treat BC as a brand‑new system. Leave GP assumptions at the door.”
“Discovery before quotes. You can’t scope what you don’t understand.”
“From 18 GP apps to 4–5 in BC—cost and complexity down.”
“Power Platform is the multiplier. Automate without a dev every time.”
“Be patient with your career growth. Experience compounds into leadership.”
A Simple GP ➜ BC Readiness Checklist
- People & Process
- Data
- Platform & Integrations
- Security & Training
- Governance & Timeline
Share & Stay Connected
If today’s conversation helped you, please share this post with GP peers who are considering BC.
Join the discussion on LinkedIn: GP to BC Community, and tell us: Which part of your GP setup are you most eager to simplify in BC?
๐บ Watch the Full Conversation with Shannon Mullins
Comments
Post a Comment