A great many manufacturers run their operation, or large parts of it, on spreadsheets. Moving to Odoo is a genuine and worthwhile change. This piece is about migrating a manufacturer from spreadsheets to Odoo.
What this migration really is
Migrating from spreadsheets to Odoo is not, mostly, a technical data-transfer exercise. It is the move from running an operation informally, on spreadsheets and in people's heads, to running it on a connected system. The spreadsheets are not just where data sits; they are how the manufacturer currently works. So this migration is as much about moving the way of working as about moving data. Understanding that is the start of approaching it well.
The spreadsheet data is messier than it looks
The first honest reality. The data in a manufacturer's spreadsheets, the product information, the bills of materials, the stock figures, is almost always messier than the manufacturer believes. Spreadsheets accumulate inconsistency, duplication, out-of-date entries, gaps, and informal conventions that only the people who maintain them understand. Migrating this data to Odoo cannot be a straight copy, because Odoo needs structured, accurate data. The migration has to turn the messy spreadsheet data into clean, structured data, and that is real work, the data has to be decided on, cleaned, and shaped to Odoo's structure. A manufacturer migrating from spreadsheets should expect, and plan time for, this data work.
The migration is an opportunity to get the data right
The flip side of the messy data is an opportunity. The migration is the one good moment to get the manufacturer's foundational data, especially its bills of materials, genuinely accurate. The manufacturer is going to go through its products and BOMs to migrate them anyway; doing that thoroughly, verifying the BOMs against what is actually built, cleaning up the products, means Odoo starts on sound data. A manufacturer that treats the migration as a chance to fix the data, rather than to faithfully reproduce the spreadsheet mess, gets a far better result.
Capturing what only lives in people's heads
A manufacturer running on spreadsheets does not really run on the spreadsheets alone; it runs on the spreadsheets plus the knowledge in a few experienced people's heads, how the planning really gets done, which figures are reliable, the workarounds in play. Migrating to Odoo means capturing the genuine processes, including the parts that live only in people's heads, and setting Odoo up to support them. This is part of why the migration is about the way of working, not just the data: the informal knowledge has to be surfaced and built into how the system will run the operation.
Approach it as a real implementation
Migrating from spreadsheets to Odoo should be approached as a genuine implementation project, with all that involves: understanding the manufacturer's real operation, configuring Odoo to fit it, doing the data work properly, testing against real processes, preparing the people, and a deliberate go-live. It is not a quick switch. And it is best phased, getting a sound core live and stable, then extending, rather than trying to replace every spreadsheet at once. Approached as a real, well-run implementation, the migration from spreadsheets to Odoo delivers what the manufacturer is moving for: one connected system in place of the spreadsheet patchwork.
The takeaway
Migrating a manufacturer from spreadsheets to Odoo is the move from running informally on spreadsheets to running on a connected system, as much a change of working as a transfer of data. The spreadsheet data is messier than it looks and must be cleaned and structured, and the migration is the opportunity to get the foundational data, especially BOMs, genuinely right. The informal knowledge in people's heads has to be captured. Approach it as a real, well-run, phased implementation. For how we approach Odoo manufacturing implementations, see our ERP practice.