Before starting a legacy data migration, prepare the Odoo environment that will receive the data. Configure the required apps, fields, master records, and basic settings so your legacy data has a clear target structure. This lets you clean and standardize source records against the Odoo environment instead of preparing them in isolation. It also gives you a consistent basis for testing the import and correcting the source file before the final migration.
- Install the Odoo apps required for your business workflows, such as Sales, Inventory, CRM, or Invoicing, so the target environment has the appropriate models and fields ready for imported records.
Configure your Odoo company and core settings before importing legacy data. Set up the required company structure, currency, and basic settings so customer records are imported into the correct environment.
Activate developer mode to inspect technical field names for precise import mapping, view system metadata, and verify External IDs. This allows you to match Odoo database fields with source columns before import.
Clean and Structure Legacy Data Before Import
Migrating to Odoo is often viewed as a clean slate for business operations. However, loading uncleaned legacy files into a single database does not solve existing data quality issues. It can spread them across connected workflows instead. Because Odoo connects Sales, Inventory, Invoicing, and CRM around shared master data, corrupted or duplicated records can undermine ERP data quality downstream. Effective ERP data cleansing starts with making the source file consistent with Odoo’s import structure. Before importing, clean, structure, and consistently identify records around one core principle: import so you can re-import.
- Check the initial spreadsheet for
hidden duplicate records before processing. Duplicates often use
inconsistent naming formats (for example, Elena Varga vs.
Varga Elena, or Julian Becker vs. Becker Julian).
- Align legacy column names with Odoo’s native field labels (e.g., using Company Type or Zip) so Odoo automatically maps your data during import without manual field matching.
Check that every row has an External ID with a clean prefix. Odoo does not automatically deduplicate contacts during import. Without External IDs, a subsequent import may create a new record instead of updating the existing one.
Validate Field Mapping and Test Odoo Data
Imports
Once your spreadsheet is structured, test the Odoo data import directly within Odoo before applying it to the target database. This confirms that the system interprets your cleaned data correctly, including field mappings and relation fields. Testing helps catch errors before they create duplicates, broken links, or inconsistent records. A test import gives you a controlled point to check the file before committing the data. Review the imported records against the source data to confirm that key values, relationships, and identifiers are preserved correctly.
- Navigate to Contacts, open the Import interface, and load your prepared file. Review the import preview to verify that Odoo recognizes the columns and interprets the cleaned values correctly before running the test import.
Check that Odoo auto-matches your standardized column headers, such as Company Type and Zip, to the correct system fields without manual selection. Review the mapping before starting the test import.
Confirm that External ID is mapped for future re-imports. For multi-value fields like Tags, ensure your source values are comma-separated so Odoo parses them correctly as indicated by the interface prompt.
Click Test in the top bar to validate data types and relations without writing records to the live database. This dry run helps prevent corrupted data loads and manual post-import cleanup.
Click Import once Odoo displays the “Everything seems valid” message. This confirms that the file has passed the validation checks and can be safely written to the database.
Verify the top notification banner confirming the number of imported entries and ensure the import completed without errors. Review the new entries in the list view to validate that all contact details mapped as expected.
Use External IDs to Update Records Through Re-Imports
Business data naturally changes over time, requiring frequent updates to contact details, addresses, and custom tags. Instead of modifying records manually in the interface, rely on your initial migration spreadsheet to execute bulk updates. When you re-import a file containing existing External IDs, Odoo uses these unique keys to identify matching database records. This makes re-imports a reliable part of the Odoo data migration process, allowing Odoo to update matching records without creating duplicate entries. Following this approach keeps migration data clean and consistent, so it can be corrected and re-imported when needed.
- Modify key fields directly in your original CSV or XLSX file, such as adding complete phone numbers, while leaving all External IDs unchanged so the spreadsheet can be used for the subsequent re-import.
Select your modified spreadsheet and click Open to load the updated records into Odoo's import interface. This allows Odoo to parse the modified fields alongside the original External IDs.
Wait for the test to finish and confirm that Odoo validates the field mappings and modified contact values before applying the changes. Review the results to confirm that the updated fields are ready for import.
Click Import to apply the changes to your database, allowing Odoo to overwrite the target fields for matching External IDs without creating duplicate records. This keeps existing records updated while preserving their unique identifiers.
Search for a modified contact, such as Elena Varga, in the list view to confirm that Odoo updated the details. The record now shows the new phone number without creating a duplicate contact.
If a duplicate contact is created accidentally, select the duplicate entries from the list view, click Actions, and choose Merge to consolidate them into a single profile while preserving the associated history and linked records.
In the Merge popup window, review the contacts to be merged, select the appropriate destination contact, and click Merge Contacts to complete the consolidation.
Verify Migrated Data Across Connected Odoo Workflows
After completing the import, validate the migrated records before considering the data migration complete. Verify that customer and product records work correctly across connected Odoo workflows. This final validation confirms that cleaned source data was imported correctly and that shared master records can be used consistently in Sales, Inventory, and Invoicing without creating duplicate or inconsistent data. Catching issues at this stage helps prevent incorrect master data from affecting downstream business operations. Test the migrated data in a real business workflow to confirm that it works as expected in practice.
- Open the Sales app, create a new quotation, and select an imported contact to confirm that company details, addresses, and tax IDs are automatically populated on commercial documents.
Click Confirm to transform the quotation into a confirmed sales order, verifying that the imported contact record integrates seamlessly into active sales workflows and
downstream document generation.
- Click Create Invoice to initiate billing for the confirmed order, allowing the connected Odoo workflow to carry the imported contact and verified data into the billing document without duplicate data entry.
Select Regular invoice and click Create Draft to generate the billing document, carrying forward all verified contact and pricing details without manual data entry.
Verify Migrated Data in Customer-Facing Invoices
Once the invoice is created, verify how the migrated customer and product data appears in the final customer-facing document. Check the portal preview, invoice details, and generated PDF before sending the invoice. This final check helps catch formatting or data issues before the document reaches the customer and confirms that the imported data remains accurate both within Odoo workflows and in the documents customers receive.
- Click Preview to inspect the
customer portal layout, verifying that all imported contact details,
addresses, and line-item totals display correctly before sending. This
validates clean data mapping across the integrated workflow.
Click Back to edit mode after confirming that the customer portal renders the imported contact details and line items correctly. This returns you to the invoice for
the final checks before sending.
- Click Send to open the composer modal, verify the auto-populated details and PDF attachment for Elena Varga, then click Send to dispatch the invoice and complete the workflow verification.
Following dispatch, Odoo automatically updates the document status to Sent. This confirms that the imported customer data remained consistent throughout the workflow.
Conclusion: Build a Scalable ERP Foundation with Clean Data
A successful data migration to Odoo is more than transferring data from one system to another. It is an opportunity to establish reliable data standards across your organization. By preparing the Odoo environment, using stable External IDs for re-imports, and validating field mappings through test imports, you can reduce duplicate records and prevent data issues from spreading across connected workflows.
As demonstrated in the end-to-end workflow, clean master data can flow from a structured spreadsheet into active Sales and Invoicing processes. Preparing and validating data from the start helps keep your Odoo environment reliable, scalable, and easier to maintain as your business grows.