Migrate from Inception to Odoo CRM

Inception contacts map to Odoo res.partner records with type='contact'. Custom fields — including external database review status and health scores — migrate as Odoo custom fields. Owner resolution happens by email match against Odoo user accounts. Unmatched owners are flagged before migration.

Inception stores commercial database validation status as a contact property. Odoo has no native equivalent. The status value migrates as a custom pick-list field (x_review_status) with inactive options set for records currently under external validation. FlitStack surfaces this in the migration plan.

Inception calculates a health score for each contact based on interaction data. Odoo has no native health score field. The value migrates as a custom Integer field (x_health_score) preserving the Inception scale so historical comparisons remain valid in Odoo reports and dashboards.

Inception companies map to Odoo res.partner records with type='company'. Address fields (street, city, state, country, zip) map directly. Industry classification maps to Odoo's industry_id pick-list with value mapping applied for non-standard Inception industry values.

Inception supports parent-child company hierarchies. Odoo res.partner uses the parent_id field for the same purpose. Circular reference detection flags any loops before migration so no orphan records are created during the hierarchy load sequence.

Inception deals map to Odoo crm.lead records with type='opportunity'. Deal amount, stage, close date, probability, priority, and owner all map to their Odoo equivalents. Odoo opportunity records require the partner_id (company) to exist first, so companies load before deals in the migration sequence.

Inception deal pipelines and stages map to Odoo sales teams (team_id) and pipeline stages (stage_id) via value mapping. Stage names are configured in Odoo CRM settings to match Inception stage labels so reporting continuity is preserved. Stage-transition timestamps are stored as custom datetime fields in Odoo.

Inception logged calls and emails map to Odoo mail.message records with the appropriate subtype. The original activity timestamp becomes mail.message.date. User assignment maps via email match to Odoo user records. Call duration is preserved in a custom field when Inception records it.

Inception scheduled meetings map to Odoo calendar.event records with original start time, stop time, and duration preserved in the corresponding calendar.event fields. Meetings linked to contacts and opportunities carry the relevant Odoo record IDs after those objects are migrated first.

Inception notes map to Odoo mail.message records without a subtype, preserving the full note text and original creation timestamp in mail.message.date. Notes are linked to the parent contact, company, or deal record in Odoo using the res_model and res_id fields for proper threading.

Inception contact labels and deal tags map to Odoo res.partner.tag and crm.tag records respectively using direct value mapping by tag name. Tags are created in Odoo before data import so they are available for assignment during the migration run.

Inception user records are matched to Odoo res.users by email address during migration. FlitStack resolves owner assignments so every record lands with a valid Odoo user_id. Unmatched owners are flagged for manual resolution before the full migration run executes.

If Inception has custom objects beyond the standard contact/company/deal model, they map to Odoo custom models created via the UI or data files. Custom object associations that use a many-to-many relationship in Inception require a junction table in Odoo — FlitStack surfaces this in the migration plan.

Inception file attachments on contacts, companies, and deals are downloaded and re-uploaded to Odoo ir.attachment records, linked to the correct res_model and res_id. File size limits follow Odoo's configured attachment storage settings. Inline images in notes are extracted and re-hosted as attachments.