Migrate from Effort to Odoo CRM

Effort contacts map directly to Odoo res.partner records. Set company_type = 'contact' on each record. If Effort stores a primary company on the contact, link via partner_id on the res.partner after company records are created. FlitStack validates email uniqueness, creates the res.partner record with company_type = 'contact', and links to the parent company record using partner_id, preserving relational integrity in Odoo.

Effort company records map to Odoo res.partner with company_type = 'company'. The name, website, industry, and address fields transfer directly. Parent-company hierarchies in Effort map to Odoo's parent_id on res.partner. FlitStack verifies that each company’s website URL follows a valid format, maps the industry value to the corresponding Odoo industry selection, and creates parent-child relationships using Odoo's parent_id, preserving the original hierarchy within the new CRM.

Effort leads that have not progressed to an active deal become Odoo crm.lead records with type = 'lead'. The contact_name, email_from, phone, and source_id fields transfer. Owner assignment resolves via email matching to Odoo res.users. FlitStack flags leads without an owner and prompts for a fallback Odoo user, guaranteeing each lead receives a user_id, then records the lead source via Odoo's utm.source model.

Effort active deals map to Odoo crm.lead with type = 'opportunity'. The deal name becomes crm.lead.name, amount maps to expected_revenue, and the linked Effort contact or company becomes the partner_id on the Odoo opportunity. FlitStack also transfers the Effort deal’s priority and tags to Odoo crm.lead priority and tag_ids, mapping any custom stage probability to the Odoo stage’s probability field, and ensures the deal’s create_date is preserved in Odoo.

Each named pipeline stage in Effort maps to a corresponding Odoo crm.stage record. FlitStack creates Odoo stages with matching names, sequence order, and probability weights. Stage probability values in Effort transfer as the probability field on each crm.lead record. FlitStack also records the original Effort stage sequence in the Odoo stage’s description field, enabling post-migration reporting that reflects the historical stage progression.

Effort assigned_to and owner fields resolve by email address against Odoo res.users. Unmatched owners are flagged before migration — invite them to Odoo or assign their records to a fallback Odoo user. No record lands without a valid owner. FlitStack logs any owner mismatches in the migration report, providing a list of unresolved emails for manual Odoo user creation before the final data load.

Effort sales team records map to Odoo crm.team. Each Odoo team requires a leader_id (res.users) and a member_ids list. If Effort stores team-specific pipeline assignments, those map to the crm.team's stage_ids configuration in Odoo. FlitStack maps each Effort team to an Odoo crm.team, assigns the team leader as the Odoo user matching the Effort team owner, and populates member_ids from the Effort team member list, preserving the original team structure.

Effort custom properties that do not map to an Odoo standard field become Odoo custom fields on crm.lead (for deal-level properties) or res.partner (for contact-level properties). FlitStack creates each custom field under Settings > Technical > Database Structure > Models with the appropriate field type — selection, char, float, date, or boolean.

Effort logged activities map to Odoo's mail.message records attached to the crm.lead. Each message stores the author_id (resolved via email), original timestamp, and body text. Call-type activities additionally create crm.phone.call records in Odoo with direction, duration, and partner_id. FlitStack also captures the original activity type (call, email, meeting) as a custom field on the mail.message, enabling filtered views in Odoo’s activity dashboard and supporting future reporting by communication channel.

Effort notes attached to contacts, companies, or deals migrate as Odoo mail.message records with subtype_note = True. The note body transfers as the message body, author resolved via owner email, and create_date preserved as the mail.message create_date in Odoo. FlitStack also records the note author as the Odoo message’s author_id, using the Effort owner’s email to match an Odoo user, and preserves the note’s creation timestamp for audit trail completeness.

Effort file attachments on records re-upload to Odoo as ir.attachment records linked to the corresponding crm.lead or res.partner. FlitStack downloads files from Effort storage, re-uploads to Odoo's ir.attachment storage, and preserves the original filename and create_date. FlitStack also validates file size limits, re-encodes any unsupported file types for Odoo compatibility, and writes the ir.attachment’s description field with the original Effort file path for traceability.

Effort workflows, sequence rules, and automation triggers are not migratable — they have no Odoo equivalent at the data layer. FlitStack exports Effort workflow definitions as a structured reference document. Odoo Studio, server actions, and automated actions rebuild these on the destination side.