Migrate from Levitate to Odoo CRM

Levitate Contacts map to Odoo res.partner, but the split decision must be made during discovery. Contacts with a company name set and no active email conversation enrollments become Odoo res.partner records of type company. Contacts without a company or with individual-specific data (birthday, personal renewal date) become res.partner records of type individual. The Odoo partner email field is the dedupe key. We resolve any duplicate email entries before import to avoid the Odoo duplicate-partner warning. If the customer uses Odoo Contactarshave or other dedupe modules, we coordinate the import sequence with those rules.

Levitate Tags map to Odoo CRM Tags (crm.tag model). Tags are stored as a many-to-many relationship between crm.tag and res.partner in the crm.tag.rel table. We preserve the full tag taxonomy including tag creation date where extractable, and write the tag list to the crm.tag model before any partner import so the foreign key references resolve at insert time. Tags used to drive automation enrollment states (e.g., 'in-birthday-sequence') are flagged separately for the customer to decide whether they become Odoo CRM Tags or notes.

Levitate Key Dates (birthday, policy renewal, anniversary, custom age milestones) are Levitate-specific custom field types. We create custom date fields on the Odoo res.partner model before any contact import: x_birthday_date, x_policy_renewal_date, and x_custom_date_1 through x_custom_date_3 as needed. The Odoo Custom Fields module (apps.odoo.com) enables non-developer field creation from the UI; alternatively we use the Odoo ORM to create fields via XML-RPC before migration. Any Key Date field that cannot be mapped to a typed date field lands as a Char field with a warning flag in the reconciliation report.

Levitate Campaigns map to Odoo CRM crm.lead records with type=lead and a dedicated tag for campaign attribution. Campaign engagement stats (open rate, click rate, reply count) migrate as custom Float fields on the crm.lead record. Individual email performance within a campaign migrates as mail.message records linked to the corresponding crm.lead. Odoo does not have a native Campaign object in the base CRM module; campaign-level reporting requires grouping crm.lead by campaign tag or a custom reporting model.

Levitate automations cannot be exported as JSON or portable workflow definitions. We extract the automation enrollment state for each contact (which sequences they are currently enrolled in, which steps they have completed) and preserve this as a tag or note on the res.partner record so the customer's Odoo admin can re-enroll contacts in rebuilt Automated Actions. We deliver a written automation inventory document listing every active Levitate automation with its trigger (tag applied, key date reached, email opened), conditions, delay steps, and recommended Odoo Automated Action equivalent using ir.cron triggers and domain filters. Rebuilding the automations is outside standard migration scope.

Levitate email engagement history migrates to Odoo mail.message records with model=res.partner and res_id pointing to the migrated partner ID. Email subject, body (HTML), and timestamp migrate directly. Attachments migrate as ir.attachment records linked to the mail.message via the relation_field. We use Odoo's XML-RPC create() call with the partner ID resolved before each message insert so the activity timeline on the partner form reflects the full Levitate history. Odoo's mail.tracking_email model captures delivery and open status if the Odoo email gateway is configured; we note this as a post-migration configuration step.

Levitate SMS logs migrate as mail.message records with subtype=sms. The Odoo SMS module (iap_sms) or a third-party SMS provider module must be installed for the SMS subtype to render in the UI; otherwise messages appear as plain activity log entries. We extract the SMS thread from Levitate's contact view (UI-based, limited to recent messages) and write each message as a mail.message with model=res.partner and the original timestamp preserved.

Levitate contact notes migrate to Odoo note.note records linked to the res.partner via the res_model and res_id fields. Rich text formatting in Levitate notes converts to plain text during extraction; any embedded images are saved as ir.attachment records with a reference link in the note body. Levitate profile notes that were requested directly from Levitate Support migrate as note.note records with a source=levitate_support flag for audit.

Levitate call engagement logs migrate as Odoo note.note records with a subtype field or a custom Char field call_disposition__c storing the call outcome. Call duration, disposition, and recording URL (if stored as a URL reference in Levitate) migrate to custom fields on the note.note record. The Odoo VoIP module (if installed) provides first-class call logging; without it, calls appear as note entries on the partner timeline.

Levitate user accounts (owner, admin, member roles) map to Odoo res.users by email match. Levitate owner role assignments on Contact, Campaign, and Automation records resolve to the corresponding res.users ID in Odoo. If the customer uses the same email domain for Levitate and Odoo users, we match on email directly. If not, we build a user mapping table during discovery and the customer's Odoo admin provisions any unmatched users before record import begins. Levitate role definitions (admin vs member permission scopes) do not map to Odoo security groups automatically; we document the Levitate role structure for the admin to assign Odoo access rights groups post-migration.

Levitate social media posts are stored as template references with scheduling metadata rather than as structured records. There is no documented export endpoint for social content. We do not migrate social media posts. We flag any social post templates that the customer wants to preserve and recommend re-creating them in Odoo's social module (if installed) or in a dedicated social media management tool as a separate implementation task.

Handwritten card orders are managed through a third-party fulfillment integration in Levitate and do not store recipient addresses as standalone contact data. Card order history is not accessible via export. We do not migrate handwritten card records. The customer should confirm any open card orders are fulfilled in Levitate before the account is closed, and re-establish the fulfillment integration separately if needed in Odoo.