Migrate from StrategicERP to Odoo CRM

Audit and extract StrategicERP data via API and CSV exports

FlitStack AI connects to StrategicERP using API credentials scoped to read-only access. We pull all customers, suppliers, contacts, sales orders, item records, project data, and activity notes in paginated batches. For any fields not accessible via API, we use StrategicERP's built-in CSV export utility. The extraction output is a structured manifest listing record counts per object, field-level null rates, and any foreign-key relationships we identified during the schema review. This manifest becomes the baseline for the migration plan and the first checkpoint in the sample migration.

Design Odoo CRM schema and create custom fields before data lands

Before any data moves, FlitStack AI creates the Odoo custom fields required for StrategicERP's custom properties and audit fields (x_source_system_id, x_original_create_date). Pipeline stages are defined to match StrategicERP order statuses, and stage probabilities are set per stage definition. If the migration scope includes multiple StrategicERP companies, we configure Odoo multi-company access rights or provision additional databases. This step also creates the email aliases and mail gateway configuration so incoming emails auto-link to the correct partner records after migration.

Resolve owners and users by email match against Odoo res.users

StrategicERP owner IDs are matched by email against Odoo res.users. For each owner record, we check whether an Odoo user with the matching email exists. If no match is found, the record is flagged and held in a pre-migration exceptions report. Your team either pre-creates the Odoo user accounts before the migration or designates a fallback owner (a designated admin or sales manager) for all unmatched records. No record migrates without a resolved owner — the exceptions report is reviewed and resolved before the sample migration runs.

Run sample migration with field-level diff on 100–500 representative records

A representative slice — spanning customers, contacts, sales orders, and project records — migrates first into a staging Odoo database. FlitStack AI generates a field-level diff comparing source values against destination values for every mapped field. You review the diff to verify that order statuses mapped to the correct pipeline stages, custom field values populated correctly, and owner resolution applied as expected. Any mapping corrections are made to the migration plan before the full run commits. The sample migration is the gate — it must pass your sign-off before the production run begins.

Execute full migration with delta-pickup window and audit log

All remaining records migrate in dependency order: master data (countries, currencies, fiscal positions) first, then res.partner records, then crm.lead opportunities. FlitStack AI writes an audit log entry for every record operation (create, update, skip) with the source record ID and destination record ID. After the full migration completes, a 24-48 hour delta window opens — during this window, any StrategicERP records created or modified after the initial extraction are pulled and upserted into Odoo. After the delta window closes, the final reconciliation report is generated and reviewed before the source system is decommissioned.

Deliver workflow rebuild reference and post-migration support plan

StrategicERP workflows, automations, and approval chains cannot migrate to Odoo and must be rebuilt. FlitStack AI exports a structured JSON document listing every StrategicERP workflow trigger, condition, and action with the equivalent Odoo automation tool (automated actions, server actions, or Flow) identified. This document is handed off during a 60-minute review session with your Odoo administrator. Post-migration support covers 30 days of delta monitoring — any records that were missed or incorrectly mapped during the delta window are corrected at no additional charge.