If your business still relies on Microsoft Dynamics GP, ERP replacement deserves a place in your 2027 budget conversation.
That doesn’t mean you need to replace GP next year. Microsoft will continue product enhancements, regulatory and tax updates, and technical support through December 31, 2029. Security updates, if needed, will continue through April 30, 2031.
But those dates can make it feel like you have more time than you really do.
Replacing an ERP takes more than a few months. Before your new system goes live, you’ll need time to understand your requirements, evaluate your options, clean up data, plan integrations, prepare employees, and implement the system.
You’ll also need a budget. And that is one of the most common reasons ERP projects get pushed down the road. The money isn’t available this year, so the project gets postponed. Then the next budget cycle arrives, and no one has done enough groundwork to know how much to request.
Even if you don’t plan to implement a new ERP in 2027, you need a realistic idea of what you’ll spend, when you’ll spend it, and which costs need to be considered before implementation begins.
That starts with looking beyond the price of the software.
Don’t start with “What does a new ERP cost?”
Of course cost matters. If you’re responsible for the budget, one of your first questions is likely to be, “How much is this going to cost us?”
The problem is that the answer isn’t just the price of the new ERP.
A Dynamics GP replacement has costs before, during, and after implementation. Depending on the project, those may include data cleanup and migration, integrations, configuration, testing, training, internal staff time, go-live support, and eventually retiring or archiving your old GP environment.
Some of those costs will appear on the proposal. Others won’t.
Budget for the transition, not just the technology
Imagine that you receive an ERP quote and build your budget around the software subscription and implementation services. The number looks manageable.
Then the project starts.
Your team discovers an integration that wasn’t included. Years of GP data need more cleanup than expected. Finance employees have to test the new system while still doing their regular jobs. A critical report needs to be redesigned. Training requires more time than planned.
That doesn’t mean the ERP was priced incorrectly. It means the project was bigger than the original budget assumed.
Recent ERP research reinforces that risk. Panorama Consulting Group’s 2026 ERP Report found that more than a quarter of surveyed organizations exceeded their project budgets, with unexpected additional technology needs the most common reason. The organizations in the study were larger than the SMBs we typically work with, so the results aren’t a pricing benchmark. But the lesson still holds: organizations often miss costs when they don’t fully understand the technology, people, and processes surrounding the ERP.
Instead of asking:
“How much will the new ERP cost?”
Ask:
“What will it cost to get our business successfully from Dynamics GP to the new system?”
That question gives you a much stronger starting point for a budget you can defend.
What is staying on Dynamics GP really costing you?
Before deciding how much you can afford to spend on a replacement, you need something to compare it against.
And that number isn’t zero.
It’s easy to look at a system you’ve owned for years and think, “GP is already paid for.” But keeping an older ERP running still costs money. Those costs simply show up in different places.
Start with the costs you can see
Review what you’ve spent over the last few years to support your current GP environment. Depending on your setup, that could include:
- Software maintenance and support
- Servers and other infrastructure
- Database and operating system costs
- Backup and disaster recovery
- Internal IT time and outsourced support
- Upgrades and testing
- Integration and customization maintenance
- Third-party reporting and supporting applications
- Security-related costs
The goal isn’t to make staying on GP look artificially expensive. It’s to establish an honest baseline.
Some of those expenses may continue after you replace GP. Others may disappear or change. You won’t know which are which until you identify them.
Look at the work surrounding the system
Some costs are harder to spot because your employees have learned to live with them.
How much time does your team spend rekeying information, maintaining offline spreadsheets, manually preparing reports, reconciling different systems, or fixing recurring problems with aging integrations?
Those frustrations may not appear as a “Dynamics GP” line item, but they still consume resources.
Be careful, however, about turning every saved hour into promised savings. There is a difference between reducing work and reducing spending.
If a new ERP saves your controller five hours a week, you haven’t automatically reduced payroll. However, if you can redirect those hours to forecasting, analysis, or other higher-value work, you create useful capacity.
Keep the two ideas separate:
- Hard-dollar costs: Money you’re spending or purchases you expect to make.
- Capacity costs: Time and resources that could potentially be reduced or redirected.
This gives you a fairer comparison between the cost of staying with GP and the cost of replacing it.
Build your replacement budget around the costs people miss
Your ERP vendor and implementation partner should help you develop an estimate based on your requirements. But during early budgeting, you should expect to account for more than software.
Software and licensing
Make sure you understand what the proposed price includes and what might change it.
Depending on the ERP, functionality, users, transaction volume, storage, environments, or other resources may affect the pricing. Don’t look only at the first-year price. Ask how the cost could change as your business grows.
Implementation and configuration
You must configure your new ERP around the way your business needs to operate. That can include discovery, system configuration, workflows, approvals, project management, and necessary customization.
Clear requirements help you understand what the project includes, what it excludes, and what might lead to extra work.
Data cleanup and migration
Moving data isn’t simply a matter of exporting everything from GP and importing it into another system. Customer, vendor, item, and financial records may need to be cleaned up, reorganized, or mapped to a new structure.
You’ll also need to decide how much historical data should move.
Not every transaction in GP needs to live in the new ERP. You can keep older details in an accessible archive while moving open transactions and the history needed for ongoing reporting into the new system.
The more history you migrate, the more work may be required to clean, map, test, and reconcile it. Don’t pay to move years of clutter simply because it exists.
Integrations and reporting
List every important system GP exchanges information with, such as payroll, banking, CRM, tax, e-commerce, EDI, warehouse, shipping, and reporting tools.
Then look beyond the application names. Document what information moves between them, how often it moves, and what happens if the connection fails.
Apply the same discipline to reporting. Before paying to recreate every familiar GP report, determine which reports people still use, which can be retired, and which should be redesigned.
Your employees’ time
Finance, operations, and IT employees may need to participate in planning, decision-making, data validation, testing, and training. They will do this while the normal work of the business continues.
For a company with lean teams, that can become a real constraint. Consider whether employees will need temporary help, overtime, or protected time to do the project work properly.
Training, go-live, and ongoing support
Don’t let your budget stop at launch.
Employees need time to learn new processes as well as new software. Your team may need extra support during the first few weeks and financial closes. Reports and workflows may require adjustment once people begin using the system every day.
You’ll also have ongoing costs after implementation, including software, support, administration, integrations, training, and future improvements.
The goal isn’t to predict every dollar perfectly. It’s to make the major cost categories visible before you commit to a number.
Be careful about two “safe” choices that can raise your costs
When you’re replacing a system as important as Dynamics GP, it’s natural to be cautious. But two decisions that sound safer can add significant time and expense.
“Let’s migrate everything”
Many companies assume that because years of detailed history exist in GP, all of it should move.
That may not be necessary.
Older data can bring along outdated customer, vendor, item, or chart-of-accounts structures you don’t want recreated in the new system. The more history you move, the more you may need to clean, map, test, and reconcile.
Decide what employees need in the new ERP to operate the business and meet reporting and record-retention requirements. Keep other information accessible through an appropriate archive.
Make it a deliberate decision. Don’t pay to recreate years of history simply because the history exists.
“Let’s run both systems in parallel just to be safe”
Running GP and the new ERP side by side for an extended period can sound reassuring. But true parallel processing may require your accounting team to do the same work twice.
That can create overtime and additional pressure on employees already balancing implementation work with their regular responsibilities. If your chart of accounts, vendor records, payment methods, or other structures change, comparing the systems may also require more reconciliation than expected.
Every extra month the old environment remains fully operational may carry costs of its own.
Thorough testing and a well-planned cutover are essential. Rather than assuming an extended parallel run provides the safest approach, specify what to test, how to reconcile the results, and what steps you need to complete before going live.
Build a budget you can explain, not just a number you can approve
At some point, leadership is going to want a number.
The temptation is to collect ERP estimates, choose a plausible figure, and add a little extra for the unexpected. But that doesn’t tell you how reliable the budget is.
A better approach is to build it around logical assumptions.
Know what your estimate assumes
An ERP budget can look precise while still resting on unanswered questions:
- How much historical data will you migrate?
- How many integrations need to be replaced?
- Which reports must be recreated?
- Which business processes will change?
- How much employee time will testing and training require?
- How long will you maintain GP during the transition?
- Which customizations are necessary?
- Which capabilities can wait until a later phase?
You may not have every answer yet. That’s normal.
What’s important is recognizing that an unknown isn’t the same as a zero-dollar cost.
Document your assumptions and flag the areas where you need better information. As you answer questions, update estimates with more accurate figures.
Separate one-time and ongoing costs
- One-time and transition costs may include implementation, data migration, integrations, testing, training, internal project time, and go-live support.
- Ongoing costs may include software, support, administration, integrations, additional services, and future improvements.
A three- to five-year view will show when costs occur, which expenses continue after implementation, and how changes in the business could affect future spending.
Make your unknowns visible
You don’t need perfect information to include ERP replacement in the 2027 budget.
You do need to separate:
- What we know: Costs and requirements that are reasonably well established.
- What we’re estimating: Items you understand but can’t price precisely yet.
- What could change: Decisions and risks that could materially affect the budget.
That gives leadership something more useful than a single number. It shows them how the number was built and where it could move.
Don’t build your 2027 budget around one scenario
Once you have documented your assumptions, use them to build three versions of the budget.
Contracted case
This version includes costs supported by relatively firm information, such as quoted software, scoped implementation services, and other verified expenses.
If you’re early in the process, this scenario may have several blanks. That’s useful. It shows where more discovery is needed.
Expected case
This is what you realistically expect the project to cost based on the information available today.
You may know that several GP integrations need to be replaced without having final pricing. Or you may know employees will need time for testing and training without knowing exactly how much.
Estimate those costs and document the assumptions behind them. Don’t let an estimate quietly become a “known” number simply because someone entered it in a spreadsheet.
Adverse case
This scenario accounts for identified risks that could materially affect the budget.
What if you discover another integration? What if the data requires more cleanup? What if implementation takes longer and you need to maintain GP for several extra months? What if additional functionality becomes necessary?
This isn’t a worst-case exercise where everything goes wrong at once. It’s a way to identify realistic risks and assign contingency to them instead of adding an arbitrary percentage to the entire project.
Together, these scenarios give leadership a useful range:
- What can we support with firm information?
- What do we realistically expect?
- What could it cost if our most important risks occur?
A defensible ERP budget isn’t one that looks most precise. It’s the one where you can explain where the numbers came from, what they depend on, and what could change them.
If Acumatica is on your shortlist, understand what drives the price
If you’re considering Acumatica as a Dynamics GP replacement, don’t expect to estimate your software budget by counting users.
Acumatica’s pricing is based primarily on three factors: the applications you need, your expected usage and resource requirements, and your deployment choice.
That makes the budgeting conversation different from ERP products priced mainly around named-user seats.
Start with the functionality you need
The applications and modules your business requires will affect the price. Are you replacing mainly financial functionality, or do you also need distribution, manufacturing, construction, project accounting, service management, or other capabilities?
The clearer you are about your requirements, the more useful the estimate becomes.
Consider today’s usage and tomorrow’s growth
Acumatica pricing also considers expected usage and resources, including transaction levels and system capacity.
Look beyond day one. Could transaction volume grow? Might you add another company or location? Are there capabilities you’re likely to adopt after the initial implementation?
You may not need everything upfront. But your three- to five-year budget should reflect likely growth rather than today’s requirements alone.
Understand what could change the price
Ask:
- Which applications are included?
- What usage and resource assumptions is the price based on?
- What happens if you exceed them?
- Are additional storage, environments, or resources extra?
- Which third-party services are priced separately?
- How might pricing change at renewal?
The point isn’t that Acumatica pricing is unusually complicated. It’s that you shouldn’t build a budget around any ERP price without understanding the assumptions underneath it.
What should you actually budget for in 2027?
You may be thinking, “This makes sense, but we’re not replacing Dynamics GP next year.”
That’s okay.
Putting ERP replacement into your 2027 budget doesn’t necessarily mean funding the entire implementation. What belongs in the budget depends on how far along you are and when you expect to move.
If you’re still planning
Your 2027 budget may be less about buying software and more about getting ready to make a smart decision.
That could mean allocating resources to:
- Document requirements and current processes
- Identify integrations, customizations, and third-party applications
- Assess and begin cleaning up GP data
- Decide which historical data needs to move
- Evaluate potential replacements
- Obtain realistic software and implementation estimates
Some of this may require outside help. Some may primarily require employee time. Either way, account for it.
If you’re already evaluating replacements
If you’ve narrowed your choices or have a likely implementation timeframe, start budgeting for software, implementation, data migration, integrations, testing, training, internal staff time, and transition costs.
By this stage, you should also replace rough assumptions with better information.
You don’t need every detail settled. But you should know which parts of the budget are firm, which are estimates, and which decisions could materially change the cost.
Don’t let another budget cycle pass without a plan
If your 2027 budget does not include GP replacement, you might easily let another year pass before you give the project serious attention. That leaves less time for planning, selection, and implementation before Microsoft’s December 31, 2029, end of product support deadline.
You may decide that 2027 isn’t the year to implement a new ERP. That’s reasonable.
But make it a decision, not a default.
Use the 2027 budgeting process to determine what you need to learn, what preparations you should make, and what funding you need to keep moving.
You don’t need to know the exact cost of your Dynamics GP replacement today. You need enough of the right information to avoid starting from scratch when you’re ready to act.
Give yourself time to plan instead of react
Budgeting for your Dynamics GP replacement doesn’t mean having every answer today. It means giving yourself enough time to ask the right questions before the timeline decides for you.
Your 2027 plan may begin with assessing your current environment, cleaning up data, and evaluating potential replacements. Or you may be ready to move into selection and implementation.
Either way, starting now gives you more control over what you need, what you don’t, and when it makes sense to move.
Ready to put numbers around your Dynamics GP replacement?
If you’re considering Acumatica or another Dynamics GP replacement, Intelligent Technologies can help you assess your current environment, identify the costs your plan needs to include, and build a realistic path forward.
Talk with our ERP team about your Dynamics GP replacement plans.
Find out what you’re dealing with while you still have options.
Budgeting for Legacy ERP Replacement Frequently Asked Questions
How much should I budget to replace Dynamics GP?
There isn’t one reliable budget figure for every Dynamics GP replacement. Your cost will depend on the ERP you choose, the functionality you need, implementation complexity, data migration, integrations, training, internal staff time, and ongoing costs. The best starting point is to identify those requirements before trying to settle on a single number.
What costs should be included in a Dynamics GP replacement budget?
Plan for more than software and implementation fees. A comprehensive budget may include data cleanup and migration, integrations, configuration, testing, training, internal staff time, go-live support, ongoing software and support costs, and the cost of maintaining or retiring your Dynamics GP environment.
Should we budget for a Dynamics GP replacement in 2027 if we aren't ready to migrate yet?
Yes, if you expect to replace Dynamics GP in the next several years. Your 2027 budget doesn’t necessarily need to fund the entire implementation. It may instead cover planning, requirements gathering, data cleanup, ERP evaluation, implementation discovery, or other work that helps you develop a more accurate replacement budget.
When does Microsoft Dynamics GP support end?
Microsoft has announced that product enhancements, regulatory and tax updates, and technical support for Dynamics GP will end on December 31, 2029. Security updates, if needed, will continue through April 30, 2031. Those dates don’t mean every GP customer needs to migrate immediately, but they give businesses a timeline to work backward from when planning a replacement.
What Dynamics GP data should we migrate to a new ERP?
Don’t assume everything has to move. Start by identifying the data employees need for current operations, financial reporting, compliance, and other business requirements. Older transactional detail may be better retained in an accessible archive when appropriate. Migrating less history can also reduce the amount of data that needs to be cleaned, mapped, tested, and reconciled.
How far ahead should we plan for a Dynamics GP replacement?
Start early enough to evaluate systems, understand requirements, clean your data, assess integrations, budget for the project, and complete implementation without relying on a last-minute deadline. For companies targeting a move before Dynamics GP product support ends on December 31, 2029, the 2027 budgeting process is a logical time to determine what planning or implementation work needs funding.
How is Acumatica pricing calculated?
Acumatica pricing is based primarily on the applications your company needs, expected usage and resource requirements, and deployment choice. That means a useful budget estimate requires more than simply counting employees or users. You should also consider required functionality, transaction levels, resources, expected growth, and any additional services your business needs.
How can we make our ERP replacement budget more accurate?
Document the assumptions behind your numbers instead of relying on one estimate. Separate known costs from estimates and risks, then model contracted, expected, and adverse scenarios. As you complete discovery and get better information about data, integrations, requirements, and implementation scope, replace assumptions with firmer numbers.
Why I like this FAQ set
