Argus Consulting Group, USA info@arguscg.com 800-274-8791

Should You Stay on Dynamics GP or Move to Business Central? A Decision Guide for Finance Leaders

Last updated: November 18, 2026

Staying on Dynamics GP or moving to Business Central comes down to five things you can check this week, your add-ons, your reports, your integrations, who runs the system, and your calendar. Microsoft supports GP through December 31, 2029.

TL;DR: Microsoft supports Dynamics GP through December 31, 2029 and encourages a move to Business Central, but no date forces a decision this quarter. Check your add-ons, reports, integrations, and who runs the system, then pick one of three paths. Stay and optimize, stay and host in the cloud, or migrate when you’re ready.

Ask three partners and you’ll get three answers, and every one of them has something to sell. Argus supports GP and migrates clients to Business Central, so this guide isn’t built to push you either way. It’s built so a controller or a president with no IT department can sort the question without a vendor in the room.

Cost deserves its own page, and any number dropped in here would be a guess. This post covers the decision that comes before the quote. If you already have a quote in hand, our Business Central quote checklist covers what to check before you sign.

What Has Microsoft Actually Said About GP’s Future?

Microsoft’s GP servicing page says support for product enhancements, regulatory (tax) updates, and technical support ends December 31, 2029. The date used to be September 30, 2029. Security updates and patches, if needed, continue until April 30, 2031.

Two other facts shape the decision. First-time GP purchases ended April 1, 2026, but Forvis Mazars, summarizing Microsoft’s announcement, says current customers can keep using GP and buy additional licenses and functionality. And that same Microsoft page says, “We are encouraging customers to transition to Dynamics 365 Business Central.”

Encouraging. Not requiring.

How Do GP and Business Central Differ for a Small Finance Team?

Updates, customization, and reporting are where a finance team feels the gap day to day. The table below sticks to points a finance team will feel, with the source named in each row. New to Business Central? Start with what Business Central is, in plain terms.

What to compare Dynamics GP Business Central
Where it runs On-premises, or hosted by a partner Cloud first, with an on-premises option (GraVoc, July 2026)
Updates You install them. Microsoft’s upgrade page says supported upgrades come from the release one year back Two major releases each April and October, plus monthly minor updates, per Microsoft Learn
Customization Dexterity, .NET, and SQL, often by modifying the application (GraVoc) Extensions that change behavior without editing Microsoft’s base code (Syvantis)
Companies Separate company databases Multiple companies in one environment (GraVoc)
Reporting SmartList, Management Reporter, SSRS Excel add-in, Power BI, and page filters (GraVoc)
Add-ons Third-party products sold by GP partners Sold through AppSource, and many GP products have a BC version (Stoneridge, May 2025)

The partner write-ups behind the Business Central column sell Business Central, so read it as one side of the story. Microsoft’s own page does add one detail a partner brochure wouldn’t. On Business Central online, administrators can set a maintenance window and reschedule an update within the update period, but users are blocked while an update runs, and once the enforced update period starts, extensions that cause a failure may be uninstalled automatically so the update can finish.

You trade control for convenience. Some teams want that trade, especially teams that have never had anyone to schedule upgrades. Others run a close process that can’t tolerate a surprise in the first week of the month, and for them the update windows are the first thing to price out.

Customization works the same way. GP customers have often changed the application itself, which is why upgrades turn into projects. Business Central’s extension model is built to leave Microsoft’s code alone. If your GP setup leans on a custom window or a modified report that only one person understands, that’s worth knowing before any platform conversation, because it will be the longest line on the plan either way.

What Actually Moves When You Migrate?

Less than the word “migrate” suggests. Microsoft’s GP to Business Central data-mapping page lists what the cloud migration tool carries across.

  • Your chart of accounts, with the main segment becoming the account number and other segments becoming dimensions
  • General ledger summary transactions for the years you choose
  • Customers and vendors, with open receivables and payables at the amount remaining
  • Open purchase orders, though fully received and invoiced items stay behind
  • Inventory quantities and costing method as set when the migration runs
  • Checkbooks, with unreconciled bank transactions so you can finish reconciling

Detail history is optional. Microsoft describes a GP Historical Snapshot that can bring general ledger detail, receivables, payables, sales orders, receipts, and inventory transactions into extension tables, limited by an oldest snapshot year you set. It sits beside live records, not inside them.

A few edges matter. Years marked historical in GP arrive as open years in Business Central and have to be closed there. Undeposited cash receipts aren’t migrated, so deposit them in GP first. Business Central has no unit of measure schedules, so only the units come across. And if you want 1099 history, the first supported year is 2024.

Nobody has to guess at any of this. Microsoft documents it field by field, which makes it a good page to hand to your controller before a partner meeting. Read it with your own month-end in mind. Which open items would you want in the new system on day one? Which history do auditors ask for? Those two answers set the scope of the data work, and they cost nothing to write down.

Open blank binder with divider tabs, a laptop, and a brass pen on a desk, representing scoping what moves in a Dynamics GP to Business Central migration

How Do You Tell Whether You’re Ready to Move?

Sort your situation before you ask for a quote. This list is a sorting aid, not a formula, and nobody has validated a score for it.

Points that favor staying on GP for now:

  • Your reports are right and finance trusts them
  • Your team’s hours on routine work are reasonable
  • An add-on or a custom report you depend on hasn’t been checked against Business Central
  • Your next 12 months include a system-sensitive event, like an audit, a grant cycle, or an acquisition

Points that favor moving:

  • Your GP partner retired, stopped answering, or has no written plan for 2029
  • Remote access leans on VPNs or remote desktops that people complain about
  • You want updates delivered on Microsoft’s schedule instead of your own
  • Leadership wants finance data flowing into Power BI and other Microsoft tools

Count honestly. If your list leans one way, price that path first. If it splits, that is an answer too, and it’s the reason to run an assessment before spending anything. If the first point on the second list sounds familiar, see our post on what to do when your GP partner pushes a Business Central migration.

What Are Your Three Paths?

You have three, and they aren’t ranked. Each fits a different company.

Stay and optimize. Fix how your team uses the system before changing the system. The GP optimization work starts with a list of tasks that eat hours and a check against what GP already does. It buys better years on GP. It doesn’t add years to Microsoft’s calendar.

Stay and host. Move the servers to a provider and keep GP as it is. Cloud hosting puts the patching and server upkeep with someone else, which helps a company with no IT department. Your GP stays GP.

Migrate when you’re ready. A Business Central migration works best with some homework done first. A community migration checklist from June 2024 lists seven steps, and the ones that get skipped are the unglamorous ones.

  • Set the goals and scope for a first phase
  • Validate the business case beyond GP’s end date
  • Name a project team and give it real time
  • Secure an executive sponsor
  • Review every customization, add-on, integration, and business-critical report against Business Central
  • Plan for change management
  • Clean the data in GP before it moves

Argus has a stake in the third path and in the first two, so weigh our view accordingly. Here’s an example of the first answer being the right one. A healthcare organization we support runs more than 60 entities across skilled nursing and senior care facilities, and a move to Business Central would take roughly 1,200 hours of effort, growing with every acquisition. For that client, staying isn’t avoidance. It’s math.

Three finance colleagues comparing options in a decision discussion about staying on Dynamics GP or moving to Business Central

When Don’t You Need Argus?

You may not need us, or any change of partner. If your reports are right, your hours are reasonable, and your current partner answers the phone and can show you a written plan with dates through 2029, keep going. A second opinion is optional, not a requirement.

The same goes if you’ve already started a Business Central project with a partner you trust. Finish it.

For everyone else, the Argus 10-Year Commitment pledges GP support through 2036, so choosing to stay on GP doesn’t mean choosing to be alone. 33 years of GP experience sits behind that pledge, and the migration team is the same team.

What’s the Next Step?

Do three things this week, with no vendor involved.

First, list every add-on, integration, and custom report, and who built each one. Second, write down the five tasks that eat up the biggest share of your team’s hours and mark whether GP has a feature for them. Third, ask your partner for a written plan with dates through 2029 and beyond.

Then bring the lists to a free assessment, where we walk through your system and give you options, not pressure, or call (626) 403-9744. If you’d rather keep your current partner, GP support is also an option.

Questions Finance Leaders Ask Before They Decide

Is there a deadline to move?

Not one that arrives this year. Microsoft ends GP support on December 31, 2029, with security patches, if needed, through April 30, 2031. A migration plan needs lead time, so the date matters for planning, but it isn’t an emergency today.

Will we lose our history if we migrate?

Not automatically. Summary balances and open items come across, and detail history is optional through the GP Historical Snapshot Microsoft describes. Decide how far back you need to look before you set the oldest year.

Can we still buy more GP licenses?

Yes, if you’re a current customer. First-time purchases ended April 1, 2026, and Forvis Mazars says existing customers can keep buying licenses and functionality.

What happens to our add-ons?

Ask each vendor in writing. Stoneridge recommends inventorying every add-on, then checking AppSource for a Business Central version, with integrations built on GP staging tables needing a redesign for the cloud. Plan for some rework.

Do we have to move to get AI tools?

Business Central has the AI agents Microsoft is building. GP teams get automation through integrations instead, which is a different tool for a similar job, and which fits depends on the work.

How long does a move take?

Nobody can say without seeing your system. Stoneridge names the drivers as modules, number of companies, data migration choices, customizations, add-ons, reporting, and training. The more of those you have, the longer the plan.

Back to all articles

Let’s Start With a Free Assessment.
$1,500 Value. No Cost.