Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

I need to move my data from an old system to a new one

Short answer

A migration fails where the two systems disagree: field types, codes, dates, relationships and rules. Name every record type, take a full backup and export, map each field in writing, trial-load a copy, compare counts, and keep the old system untouched until the new one is signed off.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • The old system is slow, unsupported or about to be switched off.
  • I do not know how many records and tables I really have.
  • A trial import gave strange dates, missing rows or broken accented text.
  • Reports from the new system do not match the old ones.
  • Only one person understands how the old system stores things.

Why does this happen?

  1. Nobody has a full inventory

    Systems grow. Extra tables, custom fields and rules added over time are not in anyone's document, so they are missed until something does not appear in the new one.

  2. Types and formats differ

    Dates in different orders and time zones, money stored as text, phone numbers with or without country codes, and names with accents are common ways values change meaning in transit.

  3. Relationships and IDs change

    If the new system issues its own IDs, every reference to the old ID, orders to customers, invoices to orders, has to be translated, or links break silently.

  4. Business rules live in the old software

    Rounding, tax rules, status changes and numbering may be written into the old code rather than the data. The new system will not do them unless they are rebuilt.

  5. The data keeps changing during the move

    If staff keep working in the old system while the copy runs, the last day's changes are missing in the new one unless a final catch-up is planned.

What can I do about it today?

  1. Back up the old system and test the backupA backup nobody has ever restored is only a hope. Ask for a restore into a separate place.
  2. Write down what the old system holdsRecord types, rough counts and who uses each. Include reports and automatic jobs.
  3. Choose the owner of each decisionSomeone from the business decides what counts as correct for each record type.
  4. Pick a quiet date for the final switchWeekend or off-season, with a short freeze on changes.
  5. Do not switch anything off yetKeep the old system running and readable until the new one has been used for a full cycle, such as a month-end.

When should I bring someone in?

  • The data is large, linked or in a database nobody on your side can open.
  • The old system has no export or the vendor is slow to cooperate.
  • A trial migration produced errors you cannot explain.

How do I handle it?

  1. Read before touchingI take a copy of the old data and read its structure to build the inventory with the owner.
  2. Write the field mapEach source field, its target, any conversion and the rule for blanks and exceptions.
  3. Run repeatable loadsThe migration is a script I can run again, so every rehearsal is identical and fixes can be re-tested.
  4. Reconcile with the businessCounts, totals and sample records are compared, and the people who use the data check the reports they know.
  5. Final catch-up and rollbackA last load of the latest changes, with a tested way back if something is wrong.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

How long does a migration take?

It depends on how many record types there are, how clean the data is and how much testing the business can do. I give a written scope after looking at the data.

Can I keep working during it?

Usually yes, until a short freeze for the final catch-up.

What if I find a mistake after switching?

That is why the old system stays untouched and a rollback is prepared before the switch.

Should I clean data first or after?

Before, where it is quick, but never destroy the original. See also the page on cleaning exports.

How was this page made?

I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.