What to Ask Before Hiring an Acumatica Consultant

Choosing an Acumatica consultant is one of the highest-leverage decisions in an ERP project. The right one gets you live on a system that fits how you actually operate. The wrong one burns budget, moves the date three times, and leaves you running two systems in parallel while your team quietly builds spreadsheets to work around both.

The hard part is that both look identical during the sales cycle. Everyone has a polished deck, a partner badge, and a confident answer about your industry.

These are the questions that tell them apart — and, more usefully, what a good answer actually sounds like versus the ones that should end the conversation.

1. “Who specifically will be doing the work?”

This is the single most important question and the one most companies forget to ask.

The most common failure pattern in ERP consulting is straightforward: senior talent sells the project, a junior team delivers it. The expertise that convinced you to sign disappears after the kickoff call. Six months later you’re explaining your business to your third new consultant, and each one is learning your workflows on your budget.

A good answer names people, states which certifications they hold, and tells you who is accountable for your go-live. It usually includes a caveat — “I’ll lead design and configuration, and a data specialist will run the migration” — because honest staffing has moving parts.

A red flag is any answer that stays at the level of “our team” or “we have a bench of certified consultants.” If they won’t name the person, it’s because that person hasn’t been assigned yet, which means they’re selling capacity they don’t have.

Follow up with: will the person in this meeting be on the project?

2. “Which specific certifications do the people configuring our system hold?”

Certifications aren’t the whole story, but they’re the baseline — and the specific ones matter far more than the count.

“Twelve certified consultants” tells you almost nothing. What you need to know is whether the person configuring your inventory module is certified in Inventory & Order Management, and whether the person building your integrations holds REST API or OData Integration Developer.

The mapping is roughly:

• Distribution — Inventory & Order Management, plus warehouse and fulfillment depth
• Construction — Construction Business Consultant and Project Accounting; job costing and AIA billing are their own discipline
• Manufacturing — production, BOM/routing, and MRP experience specifically, not general ERP experience
• Field service — dispatch, service contracts, and mobile; this module behaves differently from the rest of the suite
• Any integration work — REST API Integration Developer or OData Integration Developer

A red flag is a firm that quotes a headline number and gets vague when you ask which certifications apply to your modules.

3. “Have you implemented Acumatica in our industry — and can we talk to that client?”

Acumatica for a construction firm and Acumatica for a distributor are, in practice, different systems. Different modules, different terminology, different definitions of “done.”

Industry experience is the difference between a consultant who understands your workflows in the first meeting and one who is learning your business while billing you for the education.

A good answer includes specifics that only someone who has done it would volunteer: how they handled retainage, or three-way matching, or a WMS cutover during peak season. And they offer a reference without being pushed.

A red flag is “we’ve worked across many industries.” That’s a way of saying not yours.

4. “How do you approach data migration?”

Data migration is where implementations go to die, and it’s the area buyers scrutinize least.

A good answer describes a documented methodology: field mapping, data cleansing, at least two trial migrations into a sandbox, validation against control totals your finance team defines, and a cutover plan with a rollback option. They’ll also tell you what they won’t migrate — closed transactions past a certain date, dead SKUs, contacts that haven’t been touched in five years — because migrating everything is usually a mistake.

A red flag is any version of “we’ll handle it toward the end.” Migration is a workstream that runs alongside configuration, not a task at the finish line. If they can’t describe trial runs, they’re planning to do it once, live, and hope.

Ask specifically: how many trial migrations, and who validates the results?

5. “What’s your position on customization?”

Acumatica is highly customizable, which is both its strength and the most common way projects go wrong.

A good answer starts with resistance. A strong consultant pushes back on customization requests, asks why the standard process doesn’t work, and reserves custom code for genuine competitive differentiators. They’ll also explain the long-term cost: every customization is something to retest at every upgrade.

A red flag is enthusiasm. If every requirement in the discovery call gets answered with “yes, we can build that,” you’re being sold billable hours. The most valuable thing a consultant says is often “you don’t need that, and here’s how the standard module already handles it.”

6. “What happens when things go wrong?”

Every implementation hits problems. What matters is the mechanism for handling them.

A good answer describes a single point of contact, a defined escalation path, and a realistic response time. They’ll be candid that things will go sideways at some point — that candor is itself a signal.

A red flag is a support-ticket system with no named human attached. That tells you how the next twelve months will feel.

7. “What does the go-live plan look like — and what’s the rollback?”

Ask to see the cutover plan concept before you sign, not after.

A good answer covers the sequencing of the final data load, who’s on site or on call during cutover weekend, what “day one working” means concretely, and — critically — under what conditions you’d roll back. A consultant who has been through a failed go-live has strong opinions about rollback criteria.

A red flag is treating go-live as a date rather than a plan.

8. “What does post-go-live support include, and for how long?”

The first 90 days after go-live decide whether your team trusts the system or builds workarounds.

A good answer specifies a defined stabilization period with the same people who did the implementation, not a handoff to a separate support org that has never seen your configuration.

A red flag is a contract that ends at go-live. Some firms disappear the moment the milestone is signed, which is precisely when your team starts finding the things that don’t work.

9. “Who owns the relationship with Acumatica — and can we separate licensing from services?”

Many buyers don’t realize these are two different relationships. Your VAR is your partner of record for licensing; services can be delivered by them or by an independent specialist.

This matters because it gives you options. If your reseller’s delivery bench is booked or lacks depth in your vertical, you can bring in a specialist without disrupting your license. We covered the full distinction in Acumatica Consultant vs. VAR.

A red flag is a firm that tells you the two are inseparable. They’re not.

10. “How do you handle integrations to our other systems?”

Almost no Acumatica implementation is standalone. CRM, ecommerce, WMS, shipping, payroll — something has to sync.

A good answer distinguishes between approaches and explains the trade-offs: an iPaaS platform like Celigo for maintainable, monitorable flows; direct REST API or OData work where it’s warranted; and honesty about which parts will need ongoing care. They’ll ask about your transaction volumes and error-handling expectations before proposing anything.

A red flag is treating integration as an afterthought or assuming a pre-built connector will work as-is. Connectors are starting points, not solutions — more on how we approach Acumatica integration work.

11. “Can you show me a realistic timeline from a comparable project?”

A consultant who has done this can walk you through what the journey actually looks like — milestones, dependencies, the decision points where projects stall.

A red flag is a timeline that was clearly built backwards from a date you mentioned. Arbitrary deadlines set before scoping is finished are among the most reliable predictors of failure. The date should be an output of the analysis, not an input to it.

12. “What would make you tell us not to hire you?”

The most revealing question on the list, and the one almost nobody asks.

A good answer exists. Real specialists have boundaries: projects outside their industry depth, timelines that can’t be met responsibly, situations where your existing partner should finish the job.

A red flag is a consultant for whom every project is a perfect fit. That’s not confidence, it’s a sales posture — and it tells you their recommendation is shaped by their pipeline rather than your situation.

Using this list

You don’t need to run all twelve as an interrogation. Questions 1, 3, 4, and 12 do most of the work — they surface staffing reality, industry depth, methodology, and honesty. If those four come back strong, the rest usually follow.

And if you’re already mid-project and the answers you’re getting now don’t resemble the answers you got during the sales cycle, that’s worth acting on early. Most failing implementations show warning signs months before anyone calls it a crisis — and a stalled project is far easier to rescue at month four than at month fourteen.

FAQ

What should I ask an Acumatica consultant before hiring them?

Start with who will actually do the work — names and certifications, not titles. Then ask about their experience in your specific industry, their data migration methodology, what happens when things go wrong, and what post-go-live support includes. The answers to those five questions predict most of how the project will go.

How can I tell if an Acumatica consultant is actually qualified?

Ask for the specific certifications held by the people who will configure your system, matched to the modules you're implementing. A distribution project needs Inventory & Order Management; construction needs Construction Business Consultant and Project Accounting; integrations need REST API or OData Integration Developer. A certified generalist who has never configured your modules is not the same as a specialist.

What are the red flags when hiring an Acumatica consultant?

The biggest ones: the person in the sales meeting won't be on the project, the go-live date was set before scoping finished, data migration is described vaguely as something handled 'toward the end,' every requirement gets answered with a customization, and nobody will give you a reference in your industry.