Migrate from SwiftCRM to Odoo CRM

SwiftCRM Contact records map to Odoo res.partner with partner_type set to 'contact'. Name, email, phone, and address fields migrate directly. Face ID protection context is preserved as a tag or custom field (e.g., swift_facing_biometric__c) so the customer's admin can classify sensitive records for Odoo access rules. Custom fields on the SwiftCRM Contact are audited per account tier and mapped to Odoo custom res.partner fields created during schema setup.

SwiftCRM's native Relationships object tracking business and family ties between contacts has no direct Odoo standard equivalent. We configure the contacts_rel module (part of Odoo Apps) or use custom Many2many fields on res.partner to preserve the relationship graph. Family and business relationship types from SwiftCRM map to named relationship categories in Odoo. The customer's admin chooses the approach during scoping based on whether the relationship graph is read-only or needs to be maintained post-migration.

SwiftCRM Appointments with client links and reminder settings map to Odoo calendar.event records. The client link becomes a Many2one to res.partner (attendee). Start and stop timestamps migrate with timezone normalization to UTC or the customer's configured Odoo timezone. Reminder settings from SwiftCRM map to Odoo alarm records attached to the calendar.event, with the reminder interval preserved in minutes.

SwiftCRM Reminders tied to specific clients or appointments map to Odoo mail.activity records. Activity type is inferred from the SwiftCRM reminder context (call, meeting, follow-up) and mapped to the corresponding Odoo activity type defined in the customer's CRM settings. We preserve the SwiftCRM reminder timestamp as the mail.activity date_deadline.

Notification history tied to client interactions in SwiftCRM migrates as mail.message records in Odoo's chatter log on the corresponding res.partner record. The original notification text becomes the message body; author is set to the migrating user or a system account if the SwiftCRM notification was platform-generated.

SwiftCRM E-Docs organized within the platform migrate as Odoo ir.attachment records linked to the corresponding res.partner (contact). We export files to a staging directory, upload them to Odoo using the /web/binary/upload_attachment controller or the ir.attachment XML-RPC endpoint, and create the res_model='res.partner', res_id=<partner_id> link for each file. File metadata (name, size, MIME type) is preserved. Reviewers praising SwiftCRM's e-doc organization receive equivalent structured document access in Odoo partner form.

SwiftCRM User accounts and basic permissions map to Odoo res.users records. We resolve SwiftCRM users by email match against the Odoo destination instance. Basic permission levels from SwiftCRM map to Odoo user groups (Internal User, Portal User) and CRM-specific access rights configured during Odoo setup. Active status and login credentials require separate handling by the customer's admin post-migration.

SwiftCRM beta-stage custom fields vary by account tier. We audit all available custom fields during scoping, identify their data types, and pre-create matching Odoo custom fields on res.partner and other relevant models before migration. Date, char, integer, and selection fields map directly. Multi-select or relationship fields require Odoo custom field creation with the appropriate field_type before data import proceeds.

If SwiftCRM stores company-level records alongside contacts, we map these to Odoo res.partner with is_company=True, and link SwiftCRM child contacts as res.partner records with parent_id pointing to the company record. This creates the proper Odoo company-contact hierarchy. If SwiftCRM does not distinguish companies from contacts, all records migrate as individual contacts with the company flag unset.

If the SwiftCRM account has deal or opportunity tracking enabled, these map to Odoo crm.lead records. Pipeline and stage information from SwiftCRM maps to Odoo CRM stage configuration. Expected revenue and close date transfer to crm.lead fields. The lead is linked to the partner record created from the SwiftCRM Contact mapping.

SwiftCRM tags or labels applied to contacts migrate to Odoo res.partner.category records (tags). We create the Odoo tags before migration and apply them to the corresponding res.partner records during import. Multi-value tags from SwiftCRM checkbox properties map to multiple Odoo tag assignments on the same partner record.

SwiftCRM create_date and write_date timestamps on all migrated records are preserved in Odoo using the ir.model.data approach or as custom fields (swift_created_at__c, swift_write_date__c) on the destination records. This preserves record age and modification history for audit purposes, since Odoo's standard create_date is set to the migration date rather than the original SwiftCRM creation date.

If SwiftCRM organizes users into teams or groups for shared client access, we map these to Odoo res.groups with the appropriate internal and external user classifications. Team membership becomes Odoo group membership, and CRM record rules are configured to enforce the same sharing model the customer used in SwiftCRM.