RBTERP

Guides › Moving from Excel to an ERP Without Losing Your Figures

Moving from Excel to an ERP Without Losing Your Figures

RBTERP team · · 4 min read

A practical plan for moving your books from spreadsheets to an ERP: the cutover date, what to bring across, in which order, and how to prove it.

RBTERP Integrations & API screen: Connect RBTERP to everything around it

Integrations & API in RBTERP, with a sample company and fictional data.

Most small businesses start in Excel, and for a while it works. The trouble begins when two people need the file at once, when a formula is overwritten and nobody notices, or when the stock sheet and the sales sheet stop agreeing. Moving to an ERP fixes these problems, but only if the figures arrive intact. This guide is about getting them across safely.

Signs you have outgrown spreadsheets

Choose a cutover date

The cutover date is the last day your old records cover. Everything up to and including that day stays in Excel. Everything after it is entered in the new system.

Pick a month-end, and if you can, a year-end or quarter-end. Your balances are checked and agreed at those points anyway, and you avoid splitting a month between two systems.

What to bring across

You do not need to re-enter years of history. You need the position on the cutover date:

Keep the old workbook, read-only, for looking things up.

Clean before you move

Moving bad data into a new system gives you a new system with bad data. Before the cutover:

  1. Remove duplicate customers, suppliers and products.
  2. Count the stock physically and correct the sheet.
  3. Reconcile every bank account to the cutover date.
  4. Agree the list of open invoices with what customers and suppliers actually owe.
  5. Make sure the trial balance balances.

The order matters

Load things in an order where each step can refer to what came before: customers, suppliers and products first, then the chart of accounts, then open invoices and bills, then stock, then bank balances, and the trial balance last.

Prove it

After loading, the new system must agree with the old one on the cutover date:

Do not start entering new transactions until these agree. A difference found on day one takes minutes to trace. The same difference found three months later takes days.

Spreadsheet habits that cause trouble

How RBTERP handles a migration

Data migration in Settings: each file is checked and reconciled at the cutover
Data migration in Settings: each file is checked and reconciled at the cutover

RBTERP has a data migration screen under Settings built around a single cutover date. You open a cutover with a reference and the date, then load nine categories in order: customers, suppliers, products, chart of accounts, open customer invoices, open supplier invoices, inventory on hand, bank balances and the trial balance. Each category has an example file showing its columns.

Files are checked strictly, and a row that fails is rejected with a reason, never silently changed:

Every opening entry is dated the cutover date and posted against an Opening Balance Equity account. When the trial balance is loaded, that account should come to exactly zero. Anything left on it is the total of what does not yet reconcile, which tells you precisely how far you are from finished.

The reconciliation at the cutover compares each control account with its detail
The reconciliation at the cutover compares each control account with its detail

If you would like this done for you, our Full Account Setup and Data Entry services cover the chart of accounts, opening balances and reconciling the trial balance.

More guides

Approvals and Workflows: Who Signs Off What

How to design approval rules for purchases, payments and other documents: approval levels, amount limits, delegation, escalation and maker-checker.

16 November 2026 · 3 min read

See RBTERP working with your own business

Pick a plan and request it, or tell us about your company and we will help you choose.