Data migration is the line item every project underestimates, and the reason is always the same: the plan covers moving records and not proving that the moved records are right. This page prices both halves.
The table, by phase and route
| Work | Cost | What it produces |
|---|---|---|
| Website or host migration | from Rs 4,999 | Files, database, DNS and email records moved |
| Profiling and mapping | Rs 75,000 - Rs 3,00,000 | Field inventory, duplicate counts, mapping rules |
| Reconciliation and sign-off | Rs 75,000 - Rs 3,00,000 | Control totals, sample audits, approval |
| Extraction and load | Rs 1,00,000 - Rs 5,00,000 | Scripts, trial loads, error handling |
| Cleansing and de-duplication | Rs 1,00,000 - Rs 6,00,000 | Standardisation, merge rules, exception list |
| Cloud migration, small estate | Rs 1,50,000 - Rs 5,00,000 | Up to ten servers moved and tested |
| Full migration, fifty thousand to five lakh records | Rs 3,50,000 - Rs 17,00,000 | All four phases, end to end |
Data-only, platform or cloud
Three different jobs wear the same name.
Data-only moves records from one system to another that already exists. The destination is known, the schema is fixed, and the work is mapping and cleansing.
Platform moves the data and changes the system holding it, which means the schema itself is being designed while the migration is being built. This is where scope expands, because every new field is a decision about old data.
Cloud moves infrastructure rather than records, though the two usually arrive together. The risks are different: networking, identity, and the order in which services are started.
Knowing which one you are buying is the difference between a fixed quote and an open one.
Why reconciliation is the product
Anyone can move rows. The value is proving the rows are correct.
That means control totals before and after: record counts by table, sum of every financial column, count of records with a missing foreign key, and a sample of fifty records checked by someone in the business.
Without those four, the migration is complete in the technical sense and unverified in the sense that matters. The first month of live use then becomes the audit, and the audit happens in front of customers.
Where the estimate breaks
Three predictable causes.
Duplicates. Two customer records for the same person, entered by two branches. Merging them is a business decision, and there are always more than the profiling suggested.
Orphans. Records that point at a parent that no longer exists. They are harmless in the old system because nothing reads them, and they break the new one because it validates.
Dates and encodings. Two-digit years, time zones, and characters that survived one database and not the next. Every one is small and all of them are found late.
The profiling phase exists to find these before they are expensive. Skipping it moves the cost into the cutover weekend, where it is paid at the worst possible rate.
The cutover plan
A migration is not finished when the data loads. It is finished when the old system is switched off.
That requires a freeze window, a final delta load for anything that changed during the trial, a rollback position that is tested rather than assumed, and a named person who signs off that the numbers agree.
Plan for the delta load. A trial load on Monday and a cutover on Friday always misses four days of transactions, and those four days are the ones a customer will ask about first.
What a fixed-scope quote looks like
A migration quote is fixed only when four things are named in it: the source systems, the record counts by table, the rules for merging duplicates, and the acceptance test that closes the job.
If any of the four is missing, the number is an opening position rather than a price. The gap is not dishonesty; it is that the provider has priced the part they can see and left the rest to a change request.
Ask for the record counts yourself before the quote is issued. A database of two hundred thousand orders and one of four thousand look identical in a scope document and differ by a factor of ten in effort.
Five questions before signing
How many source systems, and who owns each. How many records, by table. Who decides when two records are the same person. What the rollback looks like. And who signs off the control totals.
If the answers are not written down, the quote is for the extraction only, and the expensive part is still unpriced.
FAQ
Can we migrate without downtime? For most systems, no. A short freeze window is normal, and a plan that promises zero downtime usually means zero verification.
How long does a migration take? Four to eight weeks for a single source with clean data, and three to six months for a multi-source migration with cleansing.
Do we need to cleanse before migrating? You can migrate dirty data, and you will spend the next year cleaning it in the new system instead, with users watching.
What if the old system has no export? That is a real cost and it belongs in the quote. It usually means reading the database directly or rebuilding records from documents.
Is a cloud migration the same as a data migration? No. One moves infrastructure, the other moves records. Projects that need both should price them separately.
Migration work in Noida
We run migrations from Noida with reconciliation as a named phase, not an afterthought. Call 7840002466 or list the source systems through the contact page.
For the infrastructure side, the cloud migration comparison covers estate sizes and landing zones.
