If your business has run on Microsoft Dynamics GP for years, you probably know it inside out. Your finance team has its shortcuts, your reports are built, and month-end close has a rhythm everyone understands. So why change something that still works?
The honest answer is that the ground under GP is shifting. Microsoft has set out a clear Dynamics GP end of support timeline, with product support ending in December 2029 and security updates running only until April 2031. GP will not switch off on those dates, but every month after that brings more risk: no new tax and regulatory updates, fewer compatible add-ons, and a shrinking pool of people who can support it.
Microsoft’s answer for GP customers is Dynamics 365 Business Central, a cloud ERP built for small and mid-sized businesses. In this guide, we’ll walk you through why the move makes sense, how the data actually gets from GP into Business Central, which tools you’ll use, where projects usually get stuck, and what to focus on once you’re live.
Why Migrate to Dynamics 365 Business Central?
Most Dymamics GP customers we speak to aren’t unhappy with GP itself. They’re frustrated by what sits around it. A few patterns come up again and again:
- Growth creates friction. As transaction volumes rise, Dynamics GP often needs extra scripts, manual steps or SQL fixes to keep up. Each workaround adds time and another thing that can break.
- Too many separate systems. GP was designed for an office network. Connecting it to e-commerce, CRM, payroll or banking usually means a patchwork of third-party connectors, and remote access is rarely smooth.
- Reporting takes too long. Getting a clear view of profitability by department, project or customer often means exporting to Excel and rebuilding numbers by hand.
- Rising cost of ownership. Servers, SQL licences, backups, version upgrades and IT support time all add up, and none of it moves the business forward.
Business Central addresses each of these directly, which is why a Dynamics GP to Business Central migration has become the default path for most GP users.
The Benefits of Migrating to Business Central
- Work from anywhere, on any device. Because Business Central runs in Microsoft’s cloud, your team can check a customer balance, approve a purchase order or look at a sales dashboard from a laptop, tablet or phone. There’s no VPN to fight with and no remote desktop session to keep alive.
- ERP that lives inside the tools you already use. Business Central connects natively with Outlook, Excel, Teams and OneDrive. A salesperson can pull up a customer’s order history from inside an Outlook email. A finance manager can share a live ledger record in a Teams chat. Invoices and quotes go out as emails directly from the system.
- Reporting that goes far beyond account segments. In GP, your chart of accounts segments carry most of the reporting load. Business Central uses dimensions instead: flexible tags such as department, region, project or product line that you attach to transactions. You can slice results any way you need without redesigning your chart of accounts, and plug the data straight into Power BI for live dashboards.
- Stronger inventory and warehouse control. Business Central supports structured warehouse processes, from receiving and put-away to picking and shipping, with bin-level tracking. For distributors and manufacturers, that usually means fewer errors and faster order turnaround.
- Screens that fit the way each person works. Every user gets a role centre showing the tasks, lists and figures that matter to their job. Pages can be personalized by hiding fields, reordering columns or adding new ones, without calling a developer.
- No more upgrade projects. Microsoft delivers two major updates a year plus monthly improvements. You stay on the current version automatically instead of planning a costly upgrade every few years.
How to Migrate Data from GP to Dynamics 365 Business Central
Microsoft provides a built-in cloud migration tool that moves GP data into Business Central online. Before you can use it, your current setup needs to meet a few requirements:
- You must be on Dynamics GP 2015 or later. If you’re on an older release, you’ll either need to upgrade Dynamics GP first or treat the move as a fresh implementation.
- Your GP databases should run on SQL Server 2016 or later, with a database compatibility level of 130 or higher.
Once those boxes are ticked, the work breaks into two parts: what the wizard handles for you, and what you’ll need to bring across another way.
Using the Data Migration Wizard
Think of the migration wizard as a one-way bridge. It’s designed for businesses ready to make Business Central their main system of record, and it copies the core of your GP setup across in a controlled way.
Typically, it brings over:
- Your chart of accounts and account master records
- Customers, along with open receivables transactions
- Vendors, along with open payables transactions
- Inventory items
- Checkbook (bank account) master data
- Summary history from inventory, payables, receivables, purchasing and sales order processing
What it’s not designed to do is recreate your entire GP history line by line. Closed transactions and full detail from modules like purchasing, sales order processing and manufacturing generally stay behind. Account balances also arrive as totals rather than broken down by segment, so if you want those totals split across dimensions, you’ll need to post adjusting journal entries in Business Central.
This is exactly why planning matters. Knowing what the wizard covers, and what it doesn’t, lets you decide early how you’ll handle everything else.
Migrating the Rest of Your Data to Business Central
For the data the wizard leaves behind, you have several options. Most projects use a combination.
Migrate with RapidStart. RapidStart configuration packages let you prepare data in Excel and import it into Business Central in bulk. It’s useful for extra master data, custom fields, opening balances and setup templates, and it makes it easy to repeat an import during testing.
Move the GP database to Azure Data Lake. Many businesses don’t need ten years of transaction detail inside their new ERP, but they do need to be able to look it up for audits, disputes or trend analysis. Copying the GP database into Azure Data Lake keeps that history safe, searchable and off your old servers. Azure Data Factory can then automate data movement and help connect information from third-party GP add-ons.
Replicate GP data with the intelligent cloud. Replication syncs your GP data into a Business Central cloud tenant on a schedule. Your team keeps entering transactions in GP while the finance team gets used to reporting in the cloud. It works best as a stepping stone during the transition, not a permanent setup.
Keep GP as a read-only archive. Some businesses simply keep a GP instance available for lookups for a set period. It’s the simplest option, but it does mean continuing to maintain a server and licences for an ageing system.
GP Migration Methods and Tools
Here’s a quick summary of the main tools and where each one fits best:
- Cloud Migration Tool – Moves master records and open balances into Business Central. Best when you’re ready to switch over fully.
- Intelligent Cloud Replication – Keeps GP and Business Central in sync on a schedule, so teams can adjust gradually.
- RapidStart Services – Bulk imports through Excel templates, ideal for extra records, custom data and repeatable test loads.
- Azure Data Lake – Long-term, low-cost storage for historical GP data you want to keep accessible without loading it into your ERP.
Choosing the right mix depends on how much history you need, how complex your GP environment is and how quickly you want to cut over. An experienced Microsoft Dynamics partner can help you make these choices before any data moves.
Challenges You Might Experience During Migration
A move to the cloud is a real step forward, but it’s not the same as a version upgrade. GP and Business Central are different products with different designs, and that creates a few predictable hurdles.
You May Need Workarounds to Replace GP Functionality
Most mature GP systems carry a layer of customizations, Dexterity modifications, SmartLists, SQL reports and third-party add-ons built up over many years. None of these move across automatically.
The good news is that many of them turn out to be unnecessary. Business Central handles a lot of what used to need an add-on, such as approval workflows, bank reconciliation and document emailing, as standard features.
Still, some gaps are real. Business Central doesn’t offer full US payroll out of the box, and its built-in financial reporting works differently from GP’s Management Reporter. In these cases, you’ll either use an app from Microsoft AppSource, connect a specialist system, or build an extension.
The key task here is a careful review of every customization and integration you run today: what it does, who relies on it, and whether Business Central already covers it. Doing this early stops surprises later in the project.
Adapting to New Functionality
Business Central gives users far more freedom to build their own views, filter data and run reports without IT help. Dimensions, in particular, change how finance teams think about analysis. Instead of building everything into account numbers, you tag transactions and analyze them from any angle.
That’s powerful, but it’s also a genuine change for people who have used GP for fifteen or twenty years. Menus look different, processes follow a different order, and familiar reports need rebuilding.
The answer is proper training and user support, not just a one-day session before go-live. For larger teams, a phased rollout often works well: finance first, then purchasing and sales, then warehouse, so each group has time to settle in.
Converting GP Financial Records to Dynamics 365
Because this isn’t a true upgrade, financial data doesn’t simply copy across. It has to be mapped from GP’s structure into Business Central’s. In practice, that usually means several test migrations, each followed by reconciliation, before the final cutover.
Account segments need to be mapped to dimensions. Opening balances must match to the cent. Open items in receivables and payables have to tie back to your GP aging reports. And your auditors will want a clear trail showing how the numbers moved.
This is where most of the effort in a GP migration actually sits. Tools like the wizard, RapidStart and Azure Data Lake make it manageable, but only with a clear data plan agreed from day one. If you’d like to see how long each stage realistically takes, read our breakdown of the real Dynamics GP to Business Central migration timeline.
Post-Migration Considerations
Going live is a milestone, not the finish line. To get full value from Business Central, plan for these steps after cutover:
- Review the system every year. Your business will change, and Microsoft will keep adding features. A yearly review helps you adjust setups, retire workarounds and adopt new capabilities.
- Use the Power Platform. Power BI for dashboards, Power Automate for routine approvals and notifications, and Power Apps for simple custom tools can remove a surprising amount of manual work.
- Keep permissions and workflows tidy. As staff join, leave or change roles, update user permissions and approval rules so the system stays secure and processes stay efficient.
- Stay ready for updates. Test new releases in a sandbox before they reach production, especially if you use extensions or integrations. Ongoing Business Central support makes this routine rather than stressful.
Final Thoughts
Moving from Dynamics GP to Business Central is more than a software swap. It’s a chance to clear out years of workarounds, simplify your processes and give your team a system built for how businesses work today.
The businesses that get the most from the move are the ones that start early, plan their data carefully and work with people who have done it before. With more than 20 years of Microsoft Dynamics experience and 200+ clients, Nevas Technologies helps GP customers assess their current system, map out a realistic migration plan and support their teams well beyond go-live.
Ready to talk about your GP migration? Contact Nevas Technologies for a free consultation.
Frequently Asked Questions
Why is Microsoft discontinuing support for Dynamics GP?
Microsoft is concentrating its investment on cloud ERP. GP was built on older, on-premises technology that is difficult to connect with modern cloud services, AI features and mobile access. Business Central shares Microsoft’s modern platform, so new features, security improvements and integrations can be delivered continuously to every customer.
How should I start planning for this transition?
Start with an honest look at your current GP setup: version, customizations, add-ons, integrations and how much history you need to keep. From there, set a budget and a target go-live date that avoids your busiest periods and year-end. Since a typical migration takes several months and GP support ends in December 2029, businesses that plan in 2026 and 2027 will have the most choice and the least pressure. Nevas Technologies can run this assessment with you and turn it into a step-by-step migration roadmap.
Will I still be able to use Dynamics GP after 2029?
Yes. GP will keep running after support ends, but Microsoft will no longer provide product updates, tax or regulatory changes, or technical support. Security updates will continue only until April 2031. After that, your system will be increasingly exposed to security risk and compatibility problems, and finding experienced support will become harder and more expensive. In the meantime, Dynamics GP support from a partner can keep your system stable while you prepare to move.
