Most vendors make you sit through two calls before anyone says a number. These are tentative planning ranges for engagements of each shape, what moves them, and what is included — so you can budget before you talk to us. Every engagement is quoted as a fixed fee against an agreed scope, not billed by the hour.
Every figure on this page is a tentative planning range, not a quoted price and not the commercial terms of any customer engagement. They are here to help you budget and to sanity-check other quotes. Your number depends on your source system, how much history you keep, how clean the data is and how many reports you need — and it is confirmed only after a short discovery. We would rather give you a real range now than a precise-sounding number that changes later.
Nearly every project we run is one of these three, or an explicit combination of the first two.
Retire one legacy system, keep the history searchable.
Move core data from a legacy platform onto a modern ERP or HCM.
Multi-phase, multi-module migration with accuracy gates.
Currency is USD. Figures exclude applicable taxes and any third-party fees your incumbent vendor charges to release your own data.
The most cost-effective pattern we see is a hybrid: migrate only the balances and transactions your new system actually operates on, and keep the full history in an archive alongside it. It keeps the migration small and the retention complete.
When you do both, we do not quote the sum of the two. A large share of the work — extraction, profiling, mapping and reconciliation — is shared between the archive and the migration, so a bundled hybrid lands well below adding the two bands together. Ask for it as a single scope.
Archives are long-lived, so they carry a running cost after go-live. On most archival engagements an initial hosting and support term — commonly two years — is included in the fixed fee, with annual renewal after that.
Compare that against what you are paying today to keep a legacy application licensed purely so somebody can occasionally read an old record. For most organisations the archive renewal is a fraction of the licence it replaces — which is usually where the business case comes from.
Cost is driven by scope and complexity, not by hours billed. These are the levers, in roughly the order they matter.
| Driver | Towards the lower end | Towards the higher end |
|---|---|---|
| Source systems | One system, one instance | Several systems or instances to consolidate |
| Extraction route | Documented API or database access | Vendor-gated exports, undocumented schema, no support |
| History retained | A few years, structured data only | A decade or more, plus documents and attachments |
| Data quality | Clean, consistent identifiers | Duplicates, orphans, inconsistent codes, manual cleansing |
| Reporting | The standard report set | Many bespoke legacy reports rebuilt |
| Reconciliation depth | Record counts and category totals | Financial and payroll control totals, document counts |
| Compliance regime | Standard retention | HIPAA, GDPR, SOX or statutory payroll evidence |
| Attachments | None or few | Scanned documents, pay statements, W-2s, clinical notes |
More detail on this: what drives Oracle Fusion migration cost and the migration cost calculator.
We quote a fixed fee for an agreed scope rather than an open-ended day rate. If the scope changes, the change is priced and agreed — you are never watching a meter run.
A short discovery — source system, history, volumes, reporting and retention needs — is enough to convert a range on this page into a firm number.
A typical schedule is 30% at kickoff, 30% when the build is ready for your validation, 20% after you approve the data, and 20% at go-live. You pay as value lands, not up front.
Enterprise programmes are priced per phase, each with its own accuracy gate and sign-off, so you can stop or re-scope between phases rather than committing to everything on day one.
Illustrative engagement shapes, to show how the drivers above play out. These are tentative planning figures for engagements of this type — not quoted prices, and not the commercial terms of any particular customer.
A small outpatient practice retiring a legacy EHR — around 1,200 patients, seven years of history, read-only archive with a full report set and two years of hosting and support included.
Around 200 employees and ten years of payroll history, including pay statements and W-2 documents, with search, an Employee 360° view and thirteen standard reports.
The same payroll estate, but migrating the operationally required balances and transactions into a new ERP with full reconciliation, rather than archiving only.
A four-phase, accuracy-gated migration for a large employer across roughly six months — full-scale loads, payroll and timecard reconciliation, attachment migration and hypercare through cutover.
See the delivery detail behind engagements like these in our case studies.
Estimates — tentative planning ranges, not quoted prices and not the commercial terms of any customer engagement. They are here to help you budget and to compare other quotes against, but your fixed fee is set after a short discovery that confirms source system, volumes, history, reporting and retention.
Because the risk in a data migration belongs with the people who understand the data, not with you. A fixed fee against a written scope means overruns caused by the work being harder than expected are ours, not yours. Scope changes are priced and agreed separately.
Ask for it as one scope. Extraction, profiling, mapping and reconciliation are largely shared between the two, so a bundled hybrid costs materially less than adding the two bands together — and it is usually the better architecture anyway, because it keeps the migration small and the retention complete.
Migrations have none — once the data is in your new platform, the engagement ends. Archives carry annual hosting and support, from around $2,400 a year for a small single-system archive and scaling with volume. On most archival engagements an initial term, commonly two years, is included in the fixed fee.
In practice, three things: a source vendor that makes extraction difficult or charges to release your data; attachments and documents at volume, such as scanned records, pay statements or W-2s; and a long list of bespoke legacy reports that must be rebuilt rather than retired. We triage reports during discovery precisely to keep that last one down.
Yes, regularly — as the data workstream inside a larger programme led by the customer's integrator. Partner commercials differ from the direct bands above; see Syntra for System Integrators or talk to us.
Tell us your source system, how much history you need to keep and what you have to report on. A short discovery is enough to turn any band on this page into a fixed fee.