ERP data migration

ERP data migration services checked against your old ERP before you switch.

We move customers, items, vendors, open orders, stock and history out of NetSuite or spreadsheets into your new ERP, and we scope QuickBooks and Sage moves the same way. Before the switch we compare counts and totals against the old system, fix what differs and run it again. Afterwards the old system stays read-only for history. You get a free written fit check first and a fixed quote before any data moves. On one NetSuite move we repaired 27,667 rows of sales-rep attribution and checked them against live NetSuite queries.

Move, clean first or go elsewhere

When we move your data, and when another team fits better.

Move if

You’re leaving NetSuite

Customers, items, vendors and open orders move to the new ERP, and NetSuite stays read-only for the old records. On our NetSuite replacement, the new system has been the system of record since July 2026, with NetSuite kept as read-only history.

Fit check first if

QuickBooks or Sage holds the books

Customers, vendors, items and open balances are mapped into the new ERP, and you decide in writing whether the accounting tool stays. We have connected an ERP to QuickBooks Online and built a CRM on Sage 100 data, but we have not yet moved a company off either.

Move if

The real records live in spreadsheets

Vendor exports and hand-kept workbooks go into one database. For a consumer-health brand whose numbers sat in those files, we built that database: 121 tables and about 1.24 million rows, refreshed every week.

Clean first

The old data is wrong

Duplicate customers, orders credited to the wrong rep, one outlet spelled five ways. We fix them during the move, while the old system is still there to check against. On our NetSuite move that meant 27,667 repaired sales-rep records.

Move if

Stock value has to be exact

On-hand quantities and FIFO cost layers have to agree after the move. On our NetSuite replacement, a script checks that before every release and allows zero drift.

Not us if

It’s SAP, a database copy or a website

SAP S/4HANA moves belong with an SAP partner. A like-for-like database copy suits a tool such as AWS DMS, or our server and cloud migration service, which also moves websites and CMSs (700+ websites migrated without downtime).

Server and cloud migration
Delivery examples

One ERP move and one data consolidation we delivered.

The figures come from the two projects’ code repositories, compiled in October 2026.

NetSuite replacement · US wholesale business

Out of NetSuite, with NetSuite kept for history

A US wholesale business ran on NetSuite. Since the July 2026 go-live, the ERP we built is its system of record, and NetSuite is read-only history.

  • 27,667 production rows of sales-rep attribution repaired and checked against live NetSuite queries.
  • Before every release, a script checks that on-hand stock equals the open FIFO cost layers, with zero drift allowed.
  • The July 2026 release passed 2,397 automated tests.
  • Separate sandbox and production databases, so every change runs on the sandbox first.
  • First commit in February 2026, go-live in July 2026.

    Reporting and CRM · US consumer-health brand

    Vendor exports and workbooks in one database

    A consumer-health brand kept its retail and distributor numbers in vendor exports and hand-kept workbooks. We built one database and web app that takes those feeds in every week.

    • 121 tables and about 1.24 million rows, measured in September 2026.
    • Distributor purchase lines matched to the outlets they ship to, with duplicates merged.
    • Weekly scheduled jobs refresh the outside data sources.
    • A reorder-prediction CRM built on the brand’s Sage 100 data.

      We do not name either client in public. Screens we share use synthetic data, never their customers, products or prices. Across all our work, we have delivered 300+ projects since 2019.

      Want the whole NetSuite story? See how we replaced NetSuite for a wholesale business.

      Get a free written fit check
      The reconciliation report

      What we compare before the switch.

      Sample layout. Every rehearsal ends with a report like this, one row per record type: what is counted in the old and new systems, which total is compared, and the rule it has to pass. When a check fails, we list the difference, fix it and run the rehearsal again before production. The rows are an example, not a report from a past project. The 27,667 repaired rows and the zero-drift stock rule are results from our NetSuite move.

      Customers
      Count in the old system against the new, after duplicates are merged, plus spot checks of named accounts and their open balances. Pass: every old customer is in the new ERP or listed as merged.
      Items
      Count of active items in each system, with units and costs checked on a sample. Pass: the counts match and no active item is missing.
      Vendors
      Count in each system, with payment terms checked on a sample. Pass: the counts match.
      Open orders
      Number of open orders and their total value in each system. Pass: both match.
      Open invoices and balances
      Number of open invoices and the total open balance per customer and per vendor in each system. Pass: the totals match to the cent.
      Stock on hand
      On-hand quantity per item and location, and the open FIFO cost layers behind it. Pass: zero drift, the rule our NetSuite replacement checks before every release.
      Rep attribution
      Which sales rep each order is credited to. On our NetSuite move, 27,667 rows were repaired. Pass: the new system gives the same answer as a live query on the old one.

      Want this report for your own records? Get a free written fit check with your old system, your new one and rough record counts.

      The move-or-leave list

      Not every record has to move.

      Moving every closed record from past years makes the move slower and the checks harder. The move-or-leave list sets out, record type by record type, what comes across and what stays readable in the old system.

      Moves
      Active customers, vendors and items, open orders, open invoices and balances, and stock on hand with its cost layers.
      Merged first
      Duplicate customers, vendors and items, merged before the move so the new ERP starts clean.
      Stays readable
      Closed orders and older history, kept read-only in the old system so anyone can still look up an old order.
      Your call
      How many years of history move. We write that down for each record type before the quote.
      Systems we move from

      ERP data migration from NetSuite, QuickBooks, Sage and spreadsheets.

      What we have done with each source system, and where it is still an offer rather than past work.

      NetSuite data migration

      On our NetSuite replacement, the new ERP has been the system of record since the July 2026 switch, and NetSuite is kept read-only for history. We repaired 27,667 production rows of sales-rep attribution and checked them against live NetSuite queries.

      QuickBooks data migration

      This one is an offer: we have not yet moved a company off QuickBooks. The fit check lists which customers, vendors, items, open orders, invoices, balances, stock and years of history would move into the new ERP, and whether QuickBooks stays as the accounting tool. We have connected an ERP to QuickBooks Online, so we have worked with its records through its API.

      Sage 100 data

      This one is an offer too: we have not yet moved a company off Sage. Sage 100 is Sage’s ERP for small and midsize businesses, and we built a reorder-prediction CRM on one brand’s Sage 100 data. A Sage move starts with the fit check naming what we would need from your setup.

      Spreadsheets and vendor exports

      When the real records sit in workbooks and vendor exports, the move starts by turning them into tables with one row per record. For a consumer-health brand whose numbers sat in those files, we built one database: 121 tables and about 1.24 million rows, with distributor lines matched to outlets and weekly jobs that refresh the outside sources.

      How we move it

      Rehearse on a sandbox until the numbers match, then switch.

      01

      Free written fit check

      Name the old system and the new one, give rough record counts, and say what must survive: open orders, balances, stock and how many years of history. Within one business day we reply in writing with what we would move first and what discovery costs.

      02

      Discovery and a fixed quote

      You get a field map from old to new, a cleanup list, the move-or-leave list and the checks we will run. Then a fixed quote and a schedule, before any data moves.

      03

      Rehearse, then switch

      We run the full move on a sandbox and compare it with the old system: counts per record type, totals such as stock on hand and open balances, and spot checks of named records. We fix the differences and repeat until they match, then move production. The old system stays read-only.

      Tell us what you are moving from and to.

      Name the old system, the new ERP and roughly how many customers, items and open orders you have. We reply in writing within one business day.

      Get a free written fit check
      What you get

      What you get at each step.

      • A written fit check within one business day
      • A field map, a cleanup list and a move-or-leave list
      • A reconciliation report from each rehearsal and from the final move
      • A fixed quote before any data moves
      • Migration scripts in your repository that can be run again
      Who it is for

      Businesses changing ERP that can’t lose an open order.

      Wholesale, distribution and ecommerce businesses in the US, UK, EU and Australia moving off NetSuite, QuickBooks, Sage or spreadsheets. We have not moved SAP or Microsoft Dynamics data, so if you run one of those, the fit check will say whether another team suits you better.

      Still choosing the new system? See custom ERP development and its build-or-buy test.

      Once the data is across, ERP integration keeps your store, CRM and accounting in sync with the new system.

      Selling wholesale through several channels? See what an ERP for wholesale distributors has to cover.

      Did someone else write the migration scripts or plan? A code audit checks them before they touch production.

      Old PHP or Node.js app that has to run on a current version before its data moves? See PHP and Node.js upgrades.

      Migration stalled halfway? We can take over a stalled migration instead of starting again.

      Want to see what we have built? Browse our selected work.

      FAQ

      Questions we get before people start.

      What is ERP data migration?

      Moving master data (customers, vendors, items), open transactions (orders, invoices, stock) and chosen history from the old system into the new ERP, then proving that the new one matches the old.

      Which ERP modules’ data has to move?

      Usually sales and orders, inventory, purchasing, finance (open balances) and customer records. Not all history needs to move, so the move-or-leave list names each module’s records and says which come across.

      Which tool is used for ERP data migration?

      The checks matter more than the tool. We write the move as scripts in your repository, so every rehearsal can be run again and its report compared with the last one. For a like-for-like database copy, a tool such as AWS DMS is often enough.

      How do you check that every record moved correctly?

      Rehearse on a sandbox, compare counts and totals against the old system, fix the differences and repeat. Keep the old system readable after the switch, so records that stay behind can still be looked up there.

      Can you move CRM data into the new ERP?

      Yes. Customer and contact records are mapped with everything else. On our NetSuite replacement, HubSpot is the CRM and syncs with the ERP on a schedule. We have not worked with Salesforce data, so if that is your CRM the fit check says whether another team suits you better.

      Do you migrate SAP data?

      No. SAP moves belong with an SAP partner. Our data work covers NetSuite, QuickBooks Online, Sage 100 and spreadsheets.

      How much does ERP data migration cost?

      The fit check is free, and the move gets a fixed quote after discovery. The price depends on the number of record types, the volume, how much cleanup is needed and how many rehearsals the checks take.

      What happens to our old ERP afterwards?

      It stays read-only, so anyone can still look up an old order. On our NetSuite replacement, NetSuite has been read-only history since the July 2026 go-live.

      Next step

      Find out what moving your data takes.

      Free written fit check within one business day. Field map and fixed price agreed before any data moves.