Dubai · Riyadh · Bahrain · Cairo · AmmanEN · AR

Guide · ERP migration · Excel, Tally, QuickBooksMoving from Excel, Tally or QuickBooks to an ERP: a step-by-step plan

The order that works: a cut-off date, clean lists, a mapped chart of accounts, opening balances that reconcile, a test run, then go-live with a trained team.

Updated 23 Oct 20269 min readUAE · Saudi Arabia · Egypt
About this guide
Topic
ERP implementation, data migration
Countries
UAE, Saudi Arabia, Egypt
Updated
23 Oct 2026
Reading time
9 minutes

Export steps checked against Tally's and Intuit's own help pages in October 2026; menus change, so follow the vendor's current help.

A company that buys an ERP is usually moving from something: a set of Excel workbooks, Tally, QuickBooks, or an older system nobody wants to open. The software is rarely what makes the move hard. The data is: lists kept by different people, balances that do not agree, history nobody can find. This guide is an ERP migration plan for moving from Excel, Tally or QuickBooks, one you can follow with any vendor, in the order that works: the cut-off date, what moves and what stays, cleaning, opening balances, a test run, training and the first close. At the end, what changes when the ERP is CorporateStack ERP.

When Excel, Tally or QuickBooks stops being enough

None of these signs is a reason on its own. Two or three together usually are.

  • Several companies or branches, put together in a workbook at every month end.
  • Approvals by email, with no record in the books of who approved a purchase or a payment.
  • Stock in more than one place, counted in a sheet that never quite matches the accounts.
  • Payroll in another tool, posted to the books as one manual journal a month.
  • e-Invoicing. In Saudi Arabia every tax invoice must come from a compliant electronic solution, and in the integration phase it is cleared or reported to ZATCA; in Egypt every invoice to a business goes through the ETA. If the current tool cannot do this, the deadline sets your date.

If the case for an ERP is still open, start with what an ERP system is and what it replaces.

The ERP migration plan, step by step

Nine steps, in this order. Each one has an owner on your side and a test that says it is done.

StepWhat happensDone when
1 · Cut-off dateThe day the new books start. The first day of a financial year is cleanest; the first day of a VAT period is the next best.The date is agreed, and everyone knows which system takes which transactions.
2 · What movesMasters, open items and balances move; closed history usually stays in the old system.A list of every file to load, each with an owner.
3 · Clean the listsDuplicates merged, inactive records marked; VAT numbers, addresses, product codes and units checked.Each owner signs off their list.
4 · Map the accountsEvery old account given a new one; companies, branches and cost centres decided now.No old account without a home.
5 · Load the mastersCustomers, suppliers, products, employees and assets through the import templates.Every row loaded, or rejected with a reason and fixed.
6 · Opening balancesThe trial balance at the cut-off, open invoices, stock by warehouse, assets with their depreciation.The new trial balance equals the old one at the cut-off.
7 · Test runA month of real documents posted on a test tenant; payroll run in parallel if it moves too.The trial balance, the VAT figures and the payroll totals match.
8 · Train by roleEach person learns the screens of their own job and is tested on them.Every user has passed their role's exam.
9 · Go liveEvery transaction from the cut-off is in the ERP; the old system becomes read-only.The first month is closed in the ERP.

What moves, and what stays behind

  • Masters: customers, suppliers, products with their units and prices, the chart of accounts, employees, assets.
  • Open items: unpaid sales and purchase invoices, open orders, cheques not yet cleared, employee loans and advances.
  • Balances at the cut-off: the trial balance, stock quantity and cost per warehouse, each asset's cost and accumulated depreciation, leave balances.
  • History: closed invoices from past years rarely need loading line by line.

Keep the old system, or a full export of it, readable for as long as the tax law of each country asks you to keep records. Load history only where a team will use it: a customer's sales by month for the sales team, last year's figures for the budget comparison.

Clean the data before it moves

Cleaning is the step that decides how long the rest takes. Do it in the old system or in the export, before anything reaches the new one.

  • Duplicates: the same customer under three spellings, the same product under two codes. Merge them, and keep the old codes in a column for the mapping.
  • Tax details: VAT registration numbers on customers and suppliers; in Saudi Arabia, the buyer's national address, which a standard tax invoice carries.
  • Products: one code, one unit of measure, a barcode where you scan, the VAT category of each product.
  • Employees: IDs, contracts, and the bank details the WPS or Mudad salary file needs.
  • Inactive records: customers who have not bought in years, suppliers you no longer use. Move them only if they carry an open balance.

Give each list one owner on your side: sales owns customers, purchasing owns suppliers, the storekeeper owns products, HR owns employees. The owner signs it off, and nobody else edits it during the move.

Opening balances: the step that decides whether the books are trusted

The opening trial balance at the cut-off is the bridge between the two systems. Loading it is quick; proving it is the work.

  1. The new trial balance at the cut-off equals the old one, account by account.
  2. Customers' open invoices add up to the receivables account, and suppliers' to the payables account.
  3. Stock quantity times cost, warehouse by warehouse, adds up to the inventory account.
  4. The asset register's cost and accumulated depreciation add up to the fixed-asset accounts.
  5. The VAT payable or refundable at the cut-off is carried, so the first return after go-live is right.

If the old books were never fully reconciled, the cut-off is where it shows. Correct the difference in the old system, or post it with a note to a suspense account and clear it before the first close. A difference that disappears into retained earnings without an explanation is the one your auditor will ask about.

Getting the data out of Excel, Tally or QuickBooks

  • Excel. The lists are already in sheets. The work is to fit each into the import template's columns: one row per record, one value per cell, and a code wherever the template asks for a code instead of a name.
  • Tally. TallyPrime exports masters, vouchers and reports to Excel or XML. Export the masters first, then the trial balance and the outstanding receivables and payables at the cut-off date.
  • QuickBooks. QuickBooks Online exports its reports and lists to Excel from Settings, under Export data, as one zip file. Take the customer, vendor and product lists, the trial balance at the cut-off, and the open invoices and unpaid bills.
  • Another system. The same order: lists, then balances at the cut-off, then open items. Ask for the export in a format your own team can read without the old vendor.

Menus change between versions, so follow the vendor's current help for the exact steps.

A test run before go-live

A parallel run, entering the same month in both systems, is the safest test and the most expensive: every document twice, by people who are also learning the new screens. A dry run is lighter. Load the masters and balances on a test tenant, post one month of real documents, and compare the trial balance and the VAT figures with the old system. Keep the parallel run for what is costly to get wrong, usually payroll, for one cycle.

Train by role, before the date

Training in the week of go-live comes too late. Each person needs the screens of their own job: the salesperson the pipeline and the quotation, the accountant the vouchers and the close, the storekeeper receipts and transfers, the approver the phone. Give each role a due date before go-live, test it, and confirm the go-live date only when the people are ready.

Go-live and the first close

Choose a go-live day away from the VAT return deadline and the payroll run. If it falls after the cut-off, enter the documents of the days in between first, so the ERP starts complete. Then close the first month in the ERP with the old system still open for reading: the first close is where a missed balance shows. After it, the old system becomes an archive.

If you are still choosing the ERP, put these steps into your request for proposal: our ERP RFP checklist has the migration questions to ask every vendor.

How CorporateStack does it

Our own people bring your records across, and the go-live date is in the proposal

In CorporateStack ERP every main list has an import page, and the error file says what to fix before anything is written. From another system, our consultants in Dubai, Riyadh, Bahrain, Cairo and Amman export, map and load your history, then reconcile: the trial balance and the customer balances match before anyone signs in. The opening balances land in ERP Core, the ledger every product posts to.

ProductThe import pages
CRMCustomers, leads, opportunities
ERP CoreProducts, suppliers, the chart of accounts, opening balances, warehouse stock, vouchers and invoices
HR & PayrollEmployees, payroll salaries, candidates
Asset ManagementAssets

Your team learns on the CorporateStack Academy: courses per role, a training tenant with sample data that resets every night, timed exams and certificates, in Arabic and English, included with every tenant. Implementation is scoped and quoted with the proposal; the date in it is the one we work to.

See CorporateStack ERP

Questions we are asked

How long does a move from Excel or Tally to an ERP take?

It depends on the number of companies and modules, and on how clean the data is, more than on the software. The plan fixes the order; the scope fixes the date. CorporateStack writes the go-live date in the proposal, once the scope is agreed.

Should we load our full history into the new ERP?

Usually not line by line. Load the masters, the open items and the balances at the cut-off. Keep the old system, or a full export of it, readable for as long as the tax law asks you to keep records, and load summarised history only where a team will use it.

What is a cut-off date in an ERP migration?

The day the new books start. Balances are taken from the old system at the end of the day before and loaded as opening balances; every transaction from the cut-off is entered in the ERP. The first day of a financial year or of a VAT period is the cleanest choice.

Do we need a parallel run?

Not for everything. A dry run on a test tenant with a month of real documents proves most of the set-up. Run in parallel only where a mistake is costly to undo, usually payroll, for one cycle.

Can we import straight from Tally or QuickBooks?

Export first. TallyPrime exports masters, vouchers and reports to Excel or XML, and QuickBooks Online exports its reports and lists to Excel. The lists then go into the ERP's import templates; in CorporateStack, the error file says what to fix before anything is written.

Plan your move with the team that runs it

A consultant loads your chart of accounts, a payroll, a few deals and a sample of your assets on one tenant set up for your country. The proposal then states the scope and the go-live date.

Book an ERP demo