Implementation · Migration

Migrating from a legacy ERP to Odoo: what actually takes the longest

The software setup is the easy part. What delays ERP migrations is data quality, change management, and decisions no one made in advance.

By Octagotech Team7 min readUpdated

Key takeaways

  • Start the data audit at least three months before your target go-live date.
  • Budget a dedicated week for chart of accounts mapping with finance leadership in the room.
  • Put the actual daily users into UAT, not just managers and power users.
  • Keep any parallel run short and bounded; with clean data and complete UAT, a cold cutover with 30 days of hypercare is usually the better trade.
  • Migrate only what the business needs to operate, and assign a dedicated internal project lead.

Every client who asks us how long an ERP migration takes hears the same answer: longer than the vendor demo implied, and rarely for the reason you expect. The software setup (configuring Odoo, wiring up integrations, building custom views) is almost never the bottleneck. What stalls migrations is the data you're bringing over and the people who have to change how they work.

This post covers where the time actually goes.

The systems we have replaced include QuickBooks and spreadsheets, with bills of materials in a separate Access database, at a custom parts manufacturer; a separate Square POS in each store at a fashion retailer; and manual billing from paper forms and legacy EMR exports at an outpatient clinic group.

The data migration reality nobody warns you about

When a business has run on the same ERP for eight or ten years, the data inside it reflects every workaround, every one-off decision, every field repurposed to mean something it was never designed to mean. A "notes" field that became a secondary part-number column. A customer account that holds three different legal entities because splitting them felt complicated at the time. Closed fiscal years where the opening balance was manually adjusted and nobody documented why.

The first thing our team does on any migration engagement is a data audit. It covers every table you plan to migrate, not a sample. What you almost always find: duplicate records (vendors entered three different ways), missing required fields (Odoo needs a country on every contact; your legacy system didn't care), and open transactions that are in a state the new system can't represent cleanly.

Open purchase orders are a particular problem. If you have 400 open POs in your legacy system and 200 of them are partially received, you can't just import them. You have to decide: recreate them in Odoo with the correct received quantities, close them in the legacy system first and start fresh, or use a cutover approach where only truly open POs come across. That decision involves procurement, finance, and operations, and it takes meetings, not just hours.

Historical data decisions add more time still. How far back do you migrate? Three years of sales orders? Seven years? Full transaction history going back to 2009? There is no universal right answer, but there is a cost: every additional year multiplies the data volume, the cleaning effort, and the testing required to verify balances match.

Chart of accounts mapping and opening balances

Finance teams consistently underestimate this phase. Mapping your existing chart of accounts to Odoo's structure sounds like a spreadsheet exercise. It is, but one that requires sign-off from your controller or CFO on every line, and those conversations surface disagreements about how things were classified in the first place.

Legacy systems often have hundreds of accounts that accumulated over years: accounts created for a project that ended, duplicate accounts for the same purpose, parent-child hierarchies that made sense in 2015 and don't reflect how the business reports today. A migration forces the cleanup, which is worth doing, but it's not fast.

Once the chart of accounts is mapped, you need opening balances. Every account needs to zero out in the old system and carry forward correctly into Odoo. If your fiscal year cutover doesn't align neatly with the go-live date (it usually doesn't), you're running a mid-year migration with partial-year balances, which requires a proper trial balance reconciliation between the two systems before anyone signs off on go-live.

Key takeaway: Start the data audit at least three months before your target go-live date. Budget a dedicated week for chart of accounts mapping with finance leadership in the room, not delegated to a junior accountant.

The change management problem is always bigger than the data problem

People who have used the same system for ten years have workflows you didn't document. Nobody is hiding anything: after a decade, the workarounds become invisible. They don't think of them as workarounds anymore. They're just how you do the thing.

We've seen warehouse teams who built entire receiving processes around a quirk in their old system's scan-and-confirm flow. We've seen sales teams whose quoting process involved exporting to Excel, doing calculations there, and re-importing, because the old system couldn't do the math and the habit stuck. These workflows surface during user acceptance testing, not during requirements gathering, because users can't always articulate a process they do automatically.

This is why the actual daily users belong in UAT, not only managers and power users. Managers know what the process is supposed to be. The person who processes 40 invoices a day knows what it actually is. Those two things are often different, and you only discover the gap when a real user tries to do their real job in the new system for the first time.

Parallel run vs. cold cutover: making the right call

Running your legacy ERP and Odoo side by side for a few weeks gives you a safety net. If something is wrong in Odoo, operations continue in the old system. It sounds like the safe choice. For many businesses, it isn't.

Parallel runs double the data entry burden on your team. Every transaction has to be entered in both systems. After two weeks, people are exhausted and making errors in both systems. Reconciling what the two systems show is itself a significant workload. And the longer the parallel run, the more "we're still running the old system" becomes an excuse to delay actually learning Odoo.

A cold cutover, where you go live on Odoo and the old system is read-only from day one, works well when your data migration was thorough, your UAT was complete, and you have support resources available at go-live. It requires more confidence but less ongoing effort. When we do run in parallel, we keep it short and bounded: two weeks at the custom-parts manufacturer, with production orders entered in both systems before go-live, and two weeks at the fashion retailer's pilot store beside Square, to verify transaction accuracy, before the other stores followed. Where the data migration and UAT are complete, a cold cutover with 30 days of hypercare, with the implementation team on call, is usually the better trade.

The parallel run makes sense when regulatory requirements demand it, when the business genuinely cannot afford a rough go-live day, or when the data migration complexity means you expect reconciliation issues that need to be caught in real time.

The phases that consistently take longer than the project plan says

Every ERP migration project plan we've seen underestimates the same phases. These phases depend on decisions and stakeholder time that are hard to predict. Here is what slips:

  • Data cleansing. Auditing the data is fast. Cleaning it requires decisions from business owners ("should we merge these two customer records or keep them separate?") that take calendar time to resolve.
  • UAT sign-off. Getting formal sign-off on each module from business owners who have day jobs is slower than any project plan assumes. Build in at least two rounds of UAT with time between them.
  • Training. One two-hour training session does not stick. Plan for training, then a gap of one to two weeks of practice, then a second training session before go-live. First-time Odoo users need to forget and relearn at least once before it becomes muscle memory.
  • Integration testing. If you're connecting Odoo to a third-party warehouse system, a payment gateway, or a custom reporting tool, plan for at least twice as many integration test cycles as you think you'll need.

What you can actually do to move faster

The most effective thing any company can do to speed up an ERP migration is start the data audit three months before go-live, not three weeks. Give the project team real authority to make data decisions, not just document them for later review. Every deferred decision is a delay.

Second: resist the urge to migrate everything. Historical data beyond three years rarely needs to live in Odoo. Archive it in your legacy system, keep the system accessible in read-only mode for a year, and migrate only what the business needs to operate going forward.

Third: assign a dedicated internal project lead, not someone doing this 20% of the time alongside their real job. ERP migrations require someone who can make decisions quickly, escalate blockers the same day, and keep stakeholders accountable to their review deadlines. That person is the single biggest predictor of whether a migration stays on schedule.

Our implementation team runs a structured pre-migration data audit as part of every engagement. It's built into the process because we learned on early projects that skipping it always costs more time than it saves. If you're in the planning stage of an Odoo migration or legacy ERP replacement, that audit is where to start.


Every business that comes to us asking about ERP migration timeline is really asking: how much disruption am I signing up for? The disruption is manageable if you plan for where time actually goes (data, decisions, and the people who have to change how they work) rather than assuming the software is the hard part. If you're evaluating an Odoo migration and want a realistic scope conversation, talk to us.

Get a realistic migration scope

The first call takes 30 minutes.

Or email sales@octagotech.com