ERP implementations fail. Not occasionally — with notable regularity, and at high cost. The reasons are well documented: scope creep, insufficient data migration planning, configuration that doesn’t match actual business processes, inadequate user training, and partners whose expertise ends at go-live, while the problems begin three months later.
The software vendor is rarely to blame. The same ERP platform delivers outstanding results in one organization and costly regret in another. The differentiating variable, almost invariably, is the implementation partner.
Selecting an ERP partner is consequently one of the higher-stakes technology decisions a CFO or technology leader makes. This guide provides the evaluation criteria that separate partners worth serious consideration from those worth avoiding.
Before evaluating partners, it’s worth being precise about the failure modes — because a good partner is specifically equipped to prevent them.
The most common point of failure is the configuration gap between what the software can do in a demo and what it does when setup for your specific business. ERP platforms are highly configurable systems. They don’t arrive pre-configured for your chart of accounts, your approval hierarchies, your project billing structure, or your revenue recognition requirements. Configuration is where expertise matters, and configuration performed by a consultant who doesn’t deeply understand your industry produces a system that technically functions but operationally frustrates.
Data migration is the second major failure point. Historical financial data, vendor records, customer data, and project information all need to migrate from legacy systems to the new platform accurately, completely, and in a format the new system can interpret. Organizations that underinvest in data preparation discover the consequences at go-live: reports that don’t reconcile, vendor payment histories that don’t match actual obligations, and chart of accounts structures that require manual correction for months after launch.
The third failure mode is change management — specifically, its absence. ERP implementations change how people work. Employees whose daily workflows are disrupted by a new system, without adequate training and support, revert to workarounds that undermine the investment. A consulting partner who delivers a configured system without investing in user adoption has delivered half an implementation.
Understanding these failure modes shapes how you evaluate partners. You’re not evaluating whether someone can configure the software — you’re evaluating whether they’ll prevent these specific outcomes.
Industry expertise that matches your business model
ERP systems must be configured to the organization’s operational model. An architecture and engineering firm bills by project, tracks utilization by resource, manages complex multi-phase contracts, and needs to understand project profitability by engagement — none of which maps neatly to a generic ERP configuration designed for a product-based manufacturer.
Deltek Vantagepoint, for example, was built specifically for project-based professional services firms. It integrates project management, resource planning, business development, and financial reporting in a single system designed for how A&E and professional services firms actually operate. A consulting partner who has implemented Deltek exclusively for project-based firms — and has 25-plus years of experience advising those firms on financial operations — brings a fundamentally different caliber of configuration than a generalist who learned the platform from documentation.
Ask prospective partners for specifics on industry experience: not general ERP experience, but the number of implementations in your specific industry, the typical size and complexity of those engagements, and the types of operational challenges they’ve helped organizations navigate. Vague answers are informative.
Accounting expertise alongside technology expertise
ERP systems are financial operations infrastructure. They manage the general ledger, accounts payable, accounts receivable, project accounting, revenue recognition, and the financial reporting that your executives rely on for business decisions. Getting the configuration right requires understanding not just how the software works, but how accounting principles apply to your specific transactions and business structure.
A consulting partner that combines deep accounting expertise with technology implementation capability produces configurations that are technically sound and financially correct. This distinction matters when the question isn’t “how do I configure this field” but “how should this transaction be recorded given our contract structure and revenue recognition policy.”
Wiss brings this combination: certified ERP advisors supported by a team of experienced accountants who understand the financial implications of configuration decisions — not just the mechanics of executing them.
Demonstrated implementation methodology
Good consulting partners have a defined methodology for how they approach implementations: how they conduct business process reviews before configuration begins, how they structure data migration planning, how they manage testing and user acceptance, and how they handle the transition from implementation to post-go-live support.
Request a detailed project plan for an implementation comparable to yours. The plan should include phases with defined deliverables, data migration milestones, testing protocols, and user training structure. A consulting partner who can’t produce a concrete methodology is telling you something about how they actually run projects.
Post-implementation support that reflects how ERP systems work in practice
ERP systems evolve. Organizational needs change, additional modules get deployed, reporting requirements shift, and technical questions arise that weren’t anticipated at go-live. The value of the ERP over its useful life depends substantially on having a partner who can support configuration adjustments, develop custom reporting as needs emerge, and provide strategic guidance on how to get more out of the investment.
Ask specifically about the post-go-live support structure: who manages support requests, what response-time standards apply, and whether the same team that implemented the system is available for ongoing support. Partners who hand off to a separate support team after go-live introduce continuity gaps that surface as unresolved tickets.
ERP vendors certify consulting partners. Certifications indicate that the partner has met the vendor’s training and competency standards, providing a baseline of confidence that the team understands the platform. What certifications don’t indicate is the depth of industry expertise, the quality of implementation methodology, or the actual outcomes the partner has delivered for clients.
Certifications are necessary but not sufficient. A partner without relevant certifications for your platform should be eliminated from consideration. A partner with certifications and no industry-specific experience is still a significant risk. The evaluation criteria above carry more predictive weight than certification status alone.
Wiss holds certification as a trusted Deltek partner and has been recognized with the 2024 Deltek Consulting MVP Award — recognition for implementation quality and client outcomes, not just platform knowledge. For NetSuite implementations, Wiss brings certified advisory experience across mid-market organizations with complex financial reporting requirements.
Start by defining the scope precisely before engaging any consulting partner. The scope should include current system architecture, data migration requirements, integration needs, the specific modules being implemented, approximate transaction volumes, and the number of users and entities involved. Vague scopes produce vague proposals that become expensive change orders.
Request proposals from two to three partners who meet the industry expertise and certification threshold. Evaluate proposals against each other on methodology specificity, timeline realism, data migration approach, and post-go-live support structure. Reference checks from clients in your specific industry — not generic references — are the most reliable predictor of what your experience will be.
The final conversation before selection should specifically address how the partner has handled implementations that encountered problems: what went wrong, how they responded, and the outcome. Every ERP implementation encounters unexpected complications. A partner’s track record of managing those complications is more informative than their track record of implementing projects that went smoothly.
Wiss’ Business Intelligence & Transformation team implements Deltek Vantagepoint and Ajera for architecture, engineering, and professional services firms, and NetSuite for mid-market organizations across industries. Both practices are supported by Wiss’s core accounting expertise — certified advisors who understand financial reporting, project accounting, and the operational requirements that determine whether an ERP investment delivers its promised return.
The service scope covers the full implementation lifecycle: business process review, software selection when the platform hasn’t been determined, project management, data migration, custom reporting and analytics, user training, and post-go-live support.
If you’re evaluating ERP implementation partners, the conversation starts with understanding your specific requirements, your current system limitations, and what successful outcomes look like for your organization. Contact Wiss’s Advisory team to begin that conversation.