Choosing an ERP feels like crossing the finish line. Months of demos, scorecards, reference calls, and board presentations finally produce a decision. For most organizations, though, selection is really the starting line. The most expensive surprises tend to appear after the contract is signed, and the partner you choose to implement the solution (if you’re using a different partner than you used for selection) has a lot to do with whether you face them at all.
Here are the most common post-selection "uh-oh" moments, and how an experienced partner helps you see them coming.
1. "Wait, that wasn't in scope?"
Scope gaps are the most frequent surprise. A requirement everyone assumed was covered, such as real-time reporting and financial visibility, workflow automation and AI, security and role-based controls, industry specific functionality turns out to be a separate module, a phase-two item, or missing entirely. This usually happens because the sales process focused on what the software can do rather than on exactly what will be configured, tested, and delivered.
A seasoned partner walks your requirements against the statement of work line by line before kickoff, surfaces hidden assumptions, and helps you close gaps while they are still inexpensive to fix.
2. "Our data is messier than we thought."
Data migration is where optimistic timelines tend to die. Duplicate vendor records, inconsistent account codes, decades of history in a legacy system, and spreadsheets living on someone's desktop all need to be cleaned, mapped and validated. Organizations routinely underestimate how much staff time this takes.
An experienced partner brings proven migration approaches, helps you decide how much history is worth converting, and schedules multiple test conversions so the go-live load is a rehearsal rather than a first attempt.
3. "It doesn't talk to our other systems."
Your ERP will need to exchange data with other platforms: eCommerce systems, CRM, BI tools, HRM, HCM, and payroll. Integrations described as "standard" during the sales cycle can turn into custom projects once the details surface.
A good partner inventories every integration early, separates what is truly out of the box from what is not, and sets realistic estimates and timelines for the rest so they are planned instead of discovered.
4. "Our people aren't ready."
Staff who have done their jobs the same way for years may resist new workflows, and leaders may underestimate the training and communication required. When change management is an afterthought, go-live brings frustration, workarounds, and a flood of help-desk tickets.
Partners who have guided many organizations through this transition know where resistance usually appears. They help build training plans, identify internal champions, and pace the rollout so people have time to adjust.
5. "Can we just make it work like the old system?"
Customization creep starts innocently: one report here, one workflow tweak there. Over time, heavy customization raises cost, slows the project, and makes every future upgrade harder. Often, the real need could be met through configuration or a modest process change.
An experienced partner knows what the software does natively and will respectfully push back when a request would recreate old problems in a new system.
6. "We're over budget and behind schedule."
Most overruns are not one big failure but many small surprises compounding: a scope gap, a slow data cleanup, an integration that took twice as long, a decision that sat for weeks. Each one adds days and dollars.
A partner with a strong track record builds realistic plans from the start, includes contingency, and runs disciplined project governance so decisions get made on time and risks are raised early.
7. "Why is our licensing bill different?"
Licensing surprises catch many organizations off guard: user counts set too low, modules priced separately, extra costs for test environments or third-party add-ons, or renewal terms nobody read closely. These can quietly add up.
A partner who knows the vendor's licensing model can help you right-size before you sign, so you neither overbuy nor discover later that you bought too little.
Why the partner matters
Every one of these problems is predictable. A partner who has implemented the same platform many times has seen these patterns before and builds safeguards into the plan from day one.
That’s why partner credentials matter. DSD Business Systems understands the challenges that come with change management, and its track record shows it:
Get ahead of it
If your organization has recently selected Acumatica Cloud ERP, or is looking for a partner to help you with the process after selection, DSD Business Systems is ready to help. We will help you determine what is needed, walk you through your project plan, and find where the common uh-ohs might be hiding, while they are still easy to fix. We’re here for you every step of the way. Contact us.
Jane Williams is an Acumatica Solutions Architect at DSD Business Systems.