Migrate from Fame Service to Odoo CRM

Pipeline contacts map directly to Odoo crm.lead records in the 'Lead' kanban state. Pipeline's create_date is preserved as a custom datetime field on the Odoo lead since Odoo's create_date reflects the migration timestamp. Original contact owner resolves by email match against Odoo res.users.

Pipeline company records map to Odoo res.partner with the is_company flag set to True. Pipeline's company domain, employee count, and annual revenue map to Odoo's website, employee_count, and revenue fields. Parent-child company hierarchies in Pipeline translate via res.partner's parent_id link.

Pipeline contacts with a company_id link map to res.partner records with is_company=False, linked to the company res.partner via parent_id. Pipeline contact properties like jobtitle and phone migrate to the corresponding res.partner fields. A Pipeline contact without a company creates a standalone res.partner contact.

Pipeline deal records map to Odoo crm.lead in the Opportunity kanban state. Pipeline dealname becomes name on the Odoo crm.lead. Pipeline amount maps to expected_revenue. Pipeline's close_date maps to date_deadline. The crm.lead's partner_id is set from the Pipeline deal's linked contact's res.partner record.

Pipeline deal stages are mapped one-to-one to Odoo stage_id values within the target crm.team. A migration plan document specifies each Pipeline stage name and its corresponding Odoo stage_id. Stage-entered timestamps from Pipeline are preserved as custom datetime fields on the Odoo opportunity for reporting continuity.

Pipeline owner_id resolves to Odoo user_id by email matching against Odoo res.users. Unmatched owners are flagged before migration so an Odoo admin can either invite them to Odoo or reassign their Pipeline records to a fallback owner. No Pipeline record migrates without a resolved user_id or explicit admin directive.

Pipeline teams map to Odoo crm.team records. The team leader in Pipeline becomes the crm.team's user_id (team leader). Team members are assigned as crm.team member records. Each crm.team in Odoo owns its own kanban pipeline and its own stage configuration.

Pipeline logged calls map to Odoo calendar.event records with subtype='Call', preserving the Pipeline call's start time, duration, and description. Pipeline meetings map similarly with subtype='Meeting'. Pipeline logged emails map to Odoo mail.message records on the crm.lead chatter, preserving subject, body, and timestamp.

Pipeline file attachments linked to deals, contacts, or companies migrate as Odoo ir.attachment records re-hosted in Odoo's filestore and linked to the parent crm.lead or res.partner. Odoo's 25MB per-file size limit applies — files exceeding 25MB are flagged for manual re-upload post-migration.

Pipeline custom properties are mapped to Odoo custom ir.model.fields entries that must be created in Odoo before the migration run. Field type matches Pipeline's original type: char for text, integer for numbers, selection for dropdowns, date for date fields. Fields without a direct Odoo equivalent are preserved as a JSON-formatted Char field for reference.

Pipeline workflows and automation rules have no Odoo equivalent in the migration payload. FlitStack exports Pipeline's automation definitions as a structured rebuild reference document, mapping each Pipeline trigger, condition, and action to the corresponding Odoo ir.actions.server or Studio automation configuration.

Pipeline tags on deals and contacts map to Odoo tag_ids on crm.lead. Tags with identical names merge automatically in Odoo. Tags that exist in Pipeline but not in Odoo are created as new Odoo tags during the migration run. Multi-value tag fields (N:N) are stored via Odoo's standard tag_ids many2many relation.