The single largest line on an ERP purchase order used to be the license. That has changed, and on a growing number of deals, implementation isn't even a separate line anymore. A wave of newer platforms is pulling implementation, data migration, and third-party integration inside the product itself, priced into the subscription rather than quoted as a services engagement on the side. That shifts the buyer's math, the systems integrator's role, and the risk profile of the whole project. It also changes what a failed rollout looks like when the vendor owns the failure end to end.
The useful question isn't whether the bundle looks cheaper on paper. It's when bundling wins and when the older, unbundled model still makes more sense.
The Old Model Priced Services Separately for a Reason
Traditional ERP deals had an internal logic to them. The vendor sold the software. A systems integrator, often one of the big consultancies and sometimes a boutique specialist, sold the work of making it fit the business. Data migration was its own workstream, integrations to the CRM and warehouse system were each scoped separately, and training was billed by the day.
This wasn't a scam. It reflected a real cost structure. Software licensing is usually a minority of total program cost, with implementation, migration, training, customization, and ongoing support absorbing the rest. Those services sat outside the license because they were bespoke work performed by different people on a different clock, not the same product the vendor was selling.
The New Model Pulls the Work Inside the Product
The bundled approach starts from a different premise. If migration templates, integration connectors, and configuration playbooks are essentially the same across customers in a given segment, why sell them as custom work every time? Package them, ship them with the platform, and price them into the subscription.
The idea isn't new. Oracle's SuiteSuccess program for NetSuite has shipped predefined components by industry and role for years. What's new is the number of vendors treating this as the default shape of the offering rather than an accelerator sold on top. Newer entrants are marketing implementation, integration, and migration as included rather than separately quoted, and recent ERP.io coverage on barchart.com is one example of that positioning.
Where the Bundle Wins
Bundling tends to be the better buy for a large slice of the mid-market. Three situations stand out:
- Standard processes. A distributor, professional services firm, or light manufacturer whose order-to-cash and procure-to-pay look like the segment norm gets most of the value the packaged configuration is designed to deliver.
- Small IT footprint. When the surrounding systems are common SaaS tools the vendor already has connectors for, the prebuilt integrations cover the real work.
- Speed over customization. For a buyer replacing accounting software on a tight timeline, a predefined rollout path is often worth more than the flexibility of a custom build.
Where the Unbundled Model Still Wins
The bundle wins by standardizing, which is also why it loses certain deals. If the business runs a genuinely unusual process, whether a specialty revenue model, a regulated workflow, or a manufacturing routing that matches no template, the packaged configuration becomes a constraint rather than an accelerator.
Migration complexity is the other place the older model earns its fee. Consolidating multiple ERPs across acquired entities, with overlapping vendor masters and inconsistent item numbering, is the kind of job where testing time (not tooling) decides whether the cutover holds. That work still belongs with people who do it for a living.
The Buyer's Diligence Has to Change With It
When services move inside the platform, the questions on the evaluation scorecard have to move with them:
- Scope of the included work. Which migrations, which integrations, and how many configuration hours are actually covered by the subscription.
- Remedies when the bundle slips. What the contract says about missed go-live dates, failed cutovers, and integrations that don't perform to spec.
- Exit and portability. How the data, integrations, and configuration may come with you if you leave, given that the work may not have been delivered as a separate, transferable asset.
- Roadmap dependency. How much of the value depends on connectors and templates the vendor still has to build for your segment.
Two Models Will Share the Market for a While
The unbundled ERP deal isn't going away. Large enterprises with genuine complexity will keep hiring integrators, and the SI market will keep evolving toward the composable, multi-vendor delivery model that shows up in frameworks like the Gartner Magic Quadrant for cloud ERP services. What's changing is the default. For a growing share of buyers, the assumption is now that migration and integration come in the box.
That reframes the buying decision. The question stops being "how much will implementation add on top?" and becomes "which vendor's opinion about how this work should be done fits our business?" Finance leaders should be ready to answer it at the next renewal or reselection.