Migrate from Swift Digital Suite to Odoo CRM

Swift Digital Suite Contacts map to Odoo res.partner records of type 'contact'. The Contact's primary email address becomes res.partner.email, phone becomes phone, and custom property values map to custom res.partner fields pre-created in Odoo. A critical dependency: Odoo requires Contacts to be associated with a parent Company (res.partner of type 'company') unless the contact is a private individual. We resolve this by creating a placeholder Company record for each unique domain in the contact email list during import, then linking all contacts from that domain to the resolved Company record.

Swift Digital Suite Segments are named behavioural or demographic groupings applied to contacts. Odoo CRM does not have a native segment object; segments map to Contact Tags via the mailing.contact model. Each segment name becomes a tag. Contacts with multiple segment memberships receive all corresponding tags. If the destination Odoo instance also uses the Odoo Marketing Automation app, segments can alternatively map to mailing.list membership records.

Swift Digital Suite Campaigns (email, event, and SMS types) map to Odoo utm.campaign records for attribution tracking. The campaign name, type, created date, and status migrate as fields on utm.campaign. Active or paused campaign state is preserved as a campaign_status field. Odoo CRM's Opportunities reference utm.campaign via the campaign_id link, enabling revenue attribution to the original Swift Digital Suite campaign.

Individual email send events (send timestamp, open, click, bounce, unsubscribe per contact-campaign pair) map to Odoo mail.message records linked to the Contact. The message type is 'email', the body contains a plain-text summary of the send event, and a custom field records the campaign reference. Open and click events that are tracked separately in Swift Digital Suite are stored as separate mail.message records with a reference back to the original send event. This preserves the full engagement timeline but requires careful ordering to maintain chronological sequence.

Survey definitions (question text, answer type, answer options) migrate to Odoo survey.survey records. Individual survey responses migrate as survey.user_input records tied to the Contact who responded. Conditional branching and skip logic defined inside Swift Digital Suite are not exposed in the export and cannot be migrated automatically; we deliver a survey structure document listing every question, its conditional dependencies, and the recommended Odoo survey builder equivalent so the customer's admin rebuilds branching manually. Multi-page surveys map to Odoo sections.

Swift Digital Suite Events (name, date, venue, ticket type) map to Odoo event.event records. Registration records, attendance status, and RSVP history map to event.registration records linked to the event and the Contact. Event-level custom fields migrate to event.event custom fields. Swift Digital Suite event check-in timestamps map to event.registration.registration_date and event.registration.attendance state fields. Ticket type from Swift Digital Suite migrates to event.event event_ticket_ids.

SMS sends tied to contacts and campaigns migrate to Odoo sms.sms records (when the Odoo SMS module is active) or to mail.message records with a custom sms_content field when SMS is not installed. The contact's SMS consent flag from Swift Digital Suite maps to res.partner.sms_opt_out. Outbound and inbound message content migrates as separate records with direction distinguished by a custom field.

Swift Digital Suite engagement scores are computed using the platform's proprietary algorithm based on open, click, and conversion events. We export the current score value as a static numeric contact property (e.g., x_engagement_score). Odoo does not have a native equivalent; the exported score serves as a historical reference value. The destination's own scoring model (if Odoo Marketing Automation is installed) recalculates independently. We document the original score alongside the new Odoo score so the customer's admin can evaluate whether the two scoring systems produce comparable outputs.

Swift Digital Suite supports custom properties on Contact and Campaign records. We extract all active custom property names, infer their data types (string, number, date, boolean, multi-select), and pre-create identically named custom fields on res.partner in Odoo before import. Where the destination field type does not support the source type directly (e.g., Swift Digital Suite multi-select becomes Odoo many2many or char with comma-separated values), we document the transformation and confirm the format with the customer before applying.

Swift Digital Suite workflow definitions (trigger conditions, time delays, action steps) are documented as structured records showing the trigger, each step, and its conditions. Odoo Studio and Odoo Marketing Automation use a different automation model (server actions, automated actions, and activity templates) that does not accept workflow definitions as importable code. We deliver a written automation inventory covering every active workflow with its trigger type, conditions, and recommended Odoo automated action or Studio server action equivalent. The customer's Odoo admin rebuilds the automations post-migration.

Swift Digital Suite tracks unsubscribe status independently for email and SMS channels. Odoo CRM uses a single opt_out boolean on res.partner that applies across all channels. We apply the more restrictive opt-out state across both channels during migration: if a contact has opted out of SMS but not email in Swift Digital Suite, we set opt_out=True in Odoo to prevent accidental re-engagement on SMS. The original channel-specific flags are preserved as custom fields x_email_unsubscribed and x_sms_unsubscribed for audit purposes.

Swift Digital Suite users referenced on contact and campaign records are matched by email against Odoo res.users. Any Swift Digital Suite owner without a matching Odoo user is flagged in a reconciliation queue. The customer's Odoo admin provisions any missing users before record import resumes, as OwnerId references are required on Odoo CRM activities and Opportunities.