GetERI
← Blog
data migrationimplementationEnterprise

Data migration from an old system: how to switch without losing history

What can be migrated (items, partners, documents, warehouses, history), in what order, how completeness is verified, and when it is better to start with a clean slate. The procedure we use during deployment.

Tibor Brič · September 18, 2026 · 2 min read

The most common reason companies stay with an old system is neither price nor features. It is fear of moving the data. This article describes how we run a migration and what is actually transferred.

What is migrated

  1. Master data: items with codes, variants and packaging, partners (customers and suppliers), price lists, warehouses and locations, users and roles.
  2. Balances: current stock levels, open orders, unpaid invoices, valid memberships and reservations.
  3. History: closed documents with their original numbers and dates, stock movements, customer history.

The order matters: master data first, then balances, and history last. Each step is verified before moving on.

Where the data comes from

From exports of the old system (CSV, XLSX, ISDOC for documents), from database backups, or through an API if the old system has one. The ERP module has import and export as a separate part, so a small company can load its master data on its own.

How completeness is verified

After each step we compare counts and totals: the number of items, the number of partners, the total of warehouse stock at purchase prices, the total of unpaid invoices. The difference must be zero, otherwise the step is repeated. This is why we do not migrate "over the weekend and see what happens".

What to leave in the old system

Sometimes it pays to migrate only master data and balances and leave the history in the old system as read-only. This applies to data older than the statutory retention period, or to systems where exporting the history costs more than it is worth. We make this decision together during the analysis.

For Enterprise deployments

For mid-size and large businesses, migration is part of a turnkey deployment: analysis on your premises, a fixed-price proposal, setup, integrations and migration, training through Edunetto, and handover. The schedule and steps are in the Enterprise section. You can see a demo system with your own data before you decide.

A small company can do it on its own: build your system, upload the master data and start.

Questions and answers

Do I have to enter items and customers manually?

No. Import from CSV, XLSX and ISDOC is part of the ERP module. For Enterprise deployments, our team performs the migration, including document history.

Is document history migrated as well?

Yes, if the old system can export it. Documents are imported as closed, with their original numbers and dates.

How long does migration take?

Hours for a small company, days for a mid-size business. In the Enterprise schedule, 14 days are allotted for setup, integrations and migration.