From Excel to ERP in 90 Days: A Phased Plan That Works

Every company I talk to about ERP has “that file”. It is called something like Clients_FINAL_v7_new.xlsx, it lives on one person’s desktop, and only that person knows which columns must never be touched. While they are at work, everything runs. When they go on holiday, the company starts guessing.
I have nothing against Excel. I have been building websites since 2001 and I have seen spreadsheets carry businesses that could not yet afford software. But there is a point where the spreadsheet stops being a tool and becomes the bottleneck. This article is the practical plan we use at Dynomica to move a business from Excel to an ERP in roughly 90 days, without stopping day-to-day work.
Signs it is time to leave the spreadsheets
There is no magic row count. There are symptoms:
- The same data is typed in two or three places (order, stock, invoice).
- Stock “in the sheet” and stock “on the shelf” rarely match.
- The monthly report takes days because someone stitches files from different teams by hand.
- There is no history of who changed what and when.
- New hires take months to get up to speed because the logic lives in people’s heads, not in a system.
If three or more of these sound familiar, an ERP is no longer a luxury. It is how you stop leaking time and money.
Why 90 days, and why two-week stages
Big ERP rollouts tend to fail for the same reason: they try to launch everything at once. People get a new system, new processes and new responsibilities on the same Monday. The result is panic, followed by a quiet return to the old file.
So we split the work into two-week stages. Each stage ends with something that actually works and that people actually use. Ninety days is about six of those stages: long enough to reach a working core, short enough that nobody loses patience.
The phased plan
Weeks 1–2: map the processes
Before we write a line of code, we sit down with the people who do the work. Not the manager who knows how things “should” be done, but the person who takes the orders and the person who ships them. We write down:
- what comes in (a request, an email, a call, a supplier file);
- who does what with it, and in what order;
- what goes out (an invoice, a shipping label, a report);
- where things get stuck.
We almost always find at least one process that exists only because “that is how we have always done it”. That one does not move into the ERP. It gets deleted.
Weeks 3–4: pick the core module
The most important decision in the whole project is where to start. My rule is simple: start where the pain is biggest and the data is clearest. For a trading business that is usually orders and inventory. For a service business it is often clients, contracts and scheduling.
I resist the urge to add “just these two other modules” up front. One core that works well beats five half-finished sections.
Weeks 5–6: migrate the data
This is where Excel takes its revenge. Expect:
- the same customer spelled four different ways;
- dates stored as text, text stored as numbers, numbers with stray spaces;
- columns whose meaning nobody remembers.
We clean the data before the migration, not after. We run a test import, the actual users check a sample of records, and only then do we move everything. Dirty data in a new system is just the old chaos with a nicer interface.
Weeks 7–8: train people and run in parallel
Training is not a one-hour slide deck. We show each person only their part of the system, using their real data. Then we run in parallel for two weeks: new entries go into the ERP while the old file stays available for reference. People see the system produces the same (or better) result before we take away the safety net.
Weeks 9–10: go live with the core
We pick a date, usually the start of a month, and announce: from today, orders are entered only in the ERP. The old file becomes read-only. In the first week we are available for questions almost in real time. Most “bugs” at this stage turn out to be habits, not software errors.
Weeks 11–12: second module and reporting
Once the core is stable, we add the next most important piece: invoicing, courier integration, management reports. This is where the ERP starts paying for itself, because the report that used to take days is now a button.
The pitfalls I see most often
- Copying the spreadsheet into software. If you simply turn the sheet into a form, you get the same problems at a higher price. An ERP is a chance to simplify the process.
- No owner on the client side. You need one person with the authority to decide. Without them, every decision waits for weeks.
- Too much customisation on day one. Standard flow first, exceptions later.
- Underestimated training. The best system fails if people work around it.
- Blind migration. Without a test import checked by real users, errors surface months later.
What we happily leave in Excel
An ERP should not kill Excel. It should send Excel back to where it belongs:
- One-off analyses and scenarios (“what if we raise prices by 5%?”).
- Budget drafts before they become an official plan.
- Personal to-do lists that affect nobody else.
- ERP exports for further number-crunching by finance.
The rule: if data is used by more than one person and changes every day, it belongs in the system. If it is for one person and one task, Excel is perfectly fine.
Off-the-shelf or custom ERP?
Off-the-shelf systems are a good start when your processes are standard. When your business wins precisely because it works differently, a custom ERP fits you instead of forcing you to fit it. At Dynomica we are a small in-house team using AI-assisted development, which lets us build module by module rather than making you wait a year for version one. You can read more about our approach on the ERP development page, and if you need something narrower, see custom software development.
The short version
- Map processes as they are, not as they should be.
- Start with one module where the pain is biggest.
- Clean the data before you migrate it.
- Train people on their own data and run in parallel for two weeks.
- Go live with the core, then add modules in two-week stages.
The goal is not to throw Excel away. The goal is for “that file” to stop being the only reason the company works.
If you want to see how many of your spreadsheets could become an ERP in 90 days, get in touch. The first conversation is usually enough to decide where to start.
Frequently asked questions
Is moving from Excel to an ERP in 90 days realistic?
Yes, if you start with one working core (usually orders and inventory, or clients and contracts) and add modules in two-week stages instead of launching everything at once.
Where should an ERP rollout start?
With the process where the pain is biggest and the data is clearest, after mapping the real processes with the people who actually do the work.
When should spreadsheet data be cleaned?
Before the migration. Run a test import, have real users check a sample, and only then move everything.
What should stay in Excel after an ERP goes live?
One-off analyses and scenarios, budget drafts, personal to-do lists and ERP exports for further analysis by finance.
What are the most common ERP implementation mistakes?
Copying spreadsheet logic one-to-one, having no decision owner on the client side, too much customisation up front, underestimated training and migrating data without checks.