Contact Info
Excel Migration
How do you migrate ERP data from Excel?
ERP migration from Excel means turning workbooks that were built for people into structured records an ERP can load: customers, suppliers, items, open orders, stock and opening balances. The hard part is not the import tool. It is deciding which version of each file is true, separating values from formulas, giving every record a unique code and reconciling totals with finance before go-live. I plan and control that work independently.
Last reviewed by Vikas Saroj
Once a business decides to move off spreadsheets, the next surprise is how hard the data is to move. Workbooks hold merged cells, color coding, notes in random columns, several versions of the same list and totals that only work because of a hidden formula. An ERP import template accepts none of that.
This page covers the data side of an ERP migration from Excel. Whether to replace spreadsheets at all is a separate question, covered on the replacing spreadsheets with ERP page. Here the decision is made, and the task is getting clean, complete and reconciled data into the new system.
I act as the independent owner of that plan, working with your finance and operations people who know the data, and with whoever configures the ERP, whether that is an implementation partner, an internal team or a freelance developer. The aim is simple: on go-live day, people should trust the numbers they see.
What I Fix
Each of these is a common reason spreadsheet data fails to import or imports wrongly.
Finding every copy of the customer list, price list or stock sheet, agreeing which one is authoritative and recording who signs it off before anything is loaded.
Turning formatted reports with merged cells, subtotals and notes into flat tables with one record per row and one value per column, the shape ERP imports require.
Giving every customer, supplier and item a unique code, merging near duplicates and setting naming rules so the ERP does not inherit the same mess on day one.
Separating calculated figures from source data, documenting the business rules behind key formulas, and rebuilding those rules as ERP configuration rather than importing their results.
Agreeing with finance how open invoices, bills, stock values and ledger balances are brought in, and proving that ERP totals match the spreadsheets at the cutover date.
Planning the moment old workbooks become read-only, so nobody keeps updating them in parallel and the business has one live source of data after go-live.
How It Runs
Know what data actually exists
List every relevant workbook
Identify owners and versions
Classify master vs open items
Agree history to keep
Make the data loadable
Flatten layouts into tables
Assign codes, remove duplicates
Map columns to ERP fields
Document formula logic
Import, reconcile and freeze
Trial imports in test
Reconcile totals with finance
Final load at cutover
Lock old spreadsheets
The symptoms usually appear the first time someone tries a test import, or worse, after go-live:
None of this means the spreadsheets were badly run. They did their job for years. They were simply never designed to be loaded into a structured system, and the migration needs to bridge that gap deliberately.
Before cleansing anything, I check which of these causes apply to your workbooks:
Knowing the causes keeps the work focused. Some files need light cleanup and a direct import, others need restructuring with the business owner, and some should be archived rather than migrated. The broader method, including trial loads and cutover planning, is covered on my ERP data migration service page.
There is no single right method. I choose per data set:
If you are still deciding whether to move at all, start with replacing spreadsheets with ERP. The ERP migration checklist lists the data sets most businesses need to cover.
All the platforms I work with provide spreadsheet import tools, with different strengths:
Industry shapes which spreadsheets matter most. Trading and wholesale businesses usually struggle with item lists, units and price lists. Manufacturing needs bills of materials and routings rebuilt, not just imported. Construction firms need active project budgets and committed costs loaded accurately. The manufacturing case study describes a move from spreadsheets to Odoo.
The effort for an ERP migration from Excel depends on the data, not the software. The main cost drivers:
The timeline runs in phases. It starts with a workbook inventory and agreement on what is in scope. Data owners then clean and restructure master data, with my templates and review. Trial imports into a test environment follow, with reconciliation after each one, repeated until totals match and users accept the results. The final load happens at cutover, opening balances are signed off by finance, and the old spreadsheets are locked so the ERP becomes the only live source.
A good first step is a short data review. Share the workbooks that run your business today, and I will map which ones hold master data, which hold open transactions and which are reports that can be retired. You get a clear picture of the cleanup needed, the risks and the decisions your team has to make before any import is attempted.
If you have not yet chosen the ERP, this review also strengthens your requirements, because the spreadsheets reveal the real business rules the system must support. If you are mid-implementation, it gives your implementation partner a cleaner starting point.
Related reading: the ERP implementation guide shows where migration fits in the overall plan. When you are ready, contact me to talk through your data. Independent ERP advice before you invest can save a great deal of rework later, and you work directly with Vikas from the first workbook review to the final reconciliation.
Tell me about your business and current systems. I’ll suggest the most sensible first step.
Book a Consultation
Not sure which ERP you need?
Share your business requirements with me and I will help you understand the right process, architecture and platform before implementation.
FAQ
Rarely. ERP imports expect one record per row, consistent data types and unique codes. Most business spreadsheets mix formatting, notes, subtotals and duplicates. Importing them as they are usually fails, or worse, succeeds and loads errors into the new system. Some cleanup and restructuring is almost always needed first.
The people who own the data should make the business decisions, such as which duplicate to keep or which price is current. I provide templates, rules, duplicate reports and review, and I can script the structural work. Ownership stays with the business because those people will live with the data after go-live.
Usually less than people expect. Most businesses migrate master data, open transactions and opening balances, then keep detailed history in an archived, read-only copy of the spreadsheets. Bringing full history into the ERP adds cleanup effort and risk, and is only worth it when reporting or compliance genuinely needs it inside the system.
They should be frozen as read-only at the cutover date and stored as an archive. If people keep updating them, the ERP and the spreadsheets drift apart and trust in the new system drops. I plan the freeze explicitly, along with the reports or views that replace each workbook people relied on.
No, only values are imported. The logic inside formulas, such as discount rules, reorder calculations or costing methods, needs to be documented and rebuilt as ERP configuration. That is often where important business rules hide, so I review key formulas early to make sure nothing the business depends on is lost.
Every business is different. Share where you are today and what you want to fix, and I’ll tell you honestly whether and how I can help.
Book a Consultation
Insights
Book a Consultation
Book a consultation to talk through your processes, systems and goals. I’ll reply with practical next steps - no obligation.
