Work from the first export
through the final review.

Start with the file your client actually sent

Upload CSV or XLSX data into a client project, choose the worksheet and inspect the parsed data. The source and your saved work stay together, so you can pick up where you left off without hunting for the right version of the spreadsheet.

Get a head start on field mapping

OdooMap compares column names, inferred types and value patterns with the target fields. It also uses mappings your reviewers previously confirmed or rejected within the same project and target model, so those decisions can inform the next set of suggestions.

When AI assistance is enabled, Claude reviews the uncertain pairings and columns still waiting for a match. It can agree with a suggestion, propose a better target or flag a doubtful match, with an explanation you can read alongside the mapping. Every result remains a suggestion until a person confirms it.

The “What the AI sees” panel shows the request and whether the provider is enabled. It includes column descriptions and target field metadata, with source cell values masked or tokenized. Built-in matching and validation remain available when AI is disabled or unavailable. Read about AI and data handling.

Catch problems while they’re still easy to fix

Mapping checks highlight missing required fields, mismatched types, selection values that don’t fit and relationships that need resolving. These checks run independently of AI as you read and save your mapping, giving you a practical list to work through before import.

Give related records a reliable way to find each other

Choose stable source keys and external IDs, then define relationships between migration steps or existing Odoo records. Validate the proposed rows before execution, including the dependencies that determine which records need to be created first.

Review the changes before they reach Odoo

Inspect the proposed values and target records, then export ordered CSV files with a manifest or ask a project administrator to approve and run supported operations. If the inputs change, the plan needs validating again. After execution, row outcomes help you investigate uncertain results before retrying.

Check the fit for your implementation

OdooMap supports CSV and XLSX sources, field mapping, supported value transformations, explicit relational references and approved create/upsert workflows. Migration plans support up to 10,000 rows and 50 steps. Binary attachments, arbitrary business actions and destructive deletes are outside the current scope.

Your Odoo version, target models, permissions and installed modules all affect how a migration behaves. Start with representative data in a sandbox, particularly where business actions have side effects that cannot be rolled back automatically.