Migrate from Act-On to Odoo CRM

Act-On Contacts map directly to Odoo Partner records. The is_company flag is set false for individual contacts. The contact's email becomes the Partner's email field and is used as the dedupe key during import. Mobile phone maps to partner.mobile; direct phone maps to partner.phone. The Act-On lifecycle stage is preserved in a custom field act_lifecycle_stage__c on the Partner record.

Act-On Companies map to Odoo Partners with is_company=True. Company name becomes Partner name; domain maps to website. Each Contact in Act-On linked to this Company receives the Odoo Partner record as its partner_id. Parent company hierarchy in Act-On Company records maps to partner.parent_id in Odoo.

Act-On Contacts that have no associated Act-On Deal and no customer lifecycle stage become Odoo CRM Lead records. Contacts with a customer lifecycle stage map to Partner records instead. We apply this routing rule during the pre-import transform and flag any Contact with both a company link and no deal history for the customer's admin to confirm during scoping.

Act-On audience Lists map to Odoo Tags on Partner (res.partner) or CRM Lead records. We export List membership as a tag name array per Contact and import as multiple res.partner.tag records linked via res.partner._ir_attachments. Static Act-On Lists migrate as literal tags; dynamic Lists are documented as a reference for Odoo's custom filter or Studio-based audience rebuild.

Act-On Deals map to Odoo CRM Opportunities. The Odoo crm.lead record is created with type='opportunity' and linked to the Company Partner record via partner_id. Deal stage maps to Odoo stage_id; the Odoo stage configuration must be created during schema design to match the customer's Act-On deal stage names and probabilities.

Each Act-On deal stage maps to an Odoo CRM Stage record scoped to the customer's pipeline. Odoo stage probability percentages migrate from Act-On to crm.stage.probability. Stage sequence order is preserved. The customer approves the stage name and probability matrix during scoping before schema deployment.

Act-On email send, open, and click events migrate to Odoo as mail.message records linked to the target Partner or CRM Lead via res_model and res_id. The email subject, body (plain text and HTML), and engagement type (sent, opened, clicked) are stored. High-volume engagement history is chunked by date range to avoid Odoo RPC timeout.

Form submission records from Act-On migrate as CRM Lead creation events with the form name and submission timestamp preserved in custom fields. The lead source field is set to the Act-On form name for attribution. Submission field values map to custom lead fields defined during schema design.

Act-On meeting engagements with start time, end time, and attendee list migrate to Odoo calendar.event records. The event is linked to the Partner (attendee) and the related Opportunity if one exists. Call duration and disposition from Act-On call records migrate to custom event fields.

Act-On note engagements migrate to Odoo mail.message records with subtype='comment' attached to the Partner or CRM Lead. Note body migrates as message_body; author information maps to the partner_id of the Act-On owner who created the note. Notes without a date are assigned the Contact's createdate timestamp.

Act-On's calculated engagement score migrates as a static numeric value in a custom float field on Partner (act_engagement_score__c). Act-On's proprietary weighting rules (opens, clicks, page visits, form submissions) do not export; we document the customer's current score range and scoring components so their Odoo admin can configure a replacement formula in Studio if needed.

Act-On Custom Data schemas define user-defined fields per Contact or Company. We read the schema definition via Act-On's Custom Objects API, export the existing field values, and write them to Odoo Partner or Lead custom fields created via Odoo Studio before migration. Field types are mapped to Odoo field types (char, float, integer, date, selection, many2one).

Act-On contact and company tags export as Odoo Partner Tags. Tag names are preserved verbatim and linked via res.partner.tag and res.partner._ir_attachments or the tag_ids many2many relation on res.partner. Tags used for campaign segmentation are preserved separately from audience List tags for reporting flexibility.

Act-On owners map to Odoo Users by email match. Any Act-On owner without a matching Odoo User is held in a reconciliation queue for the customer's admin to provision the User record before record import resumes. Inactive owners map to inactive users with a flag for the admin to activate post-migration.

Act-On Automated Programs are not migratable as code. We export the Program name, step count, step types (email, delay, condition, action), and the Contact membership list as a written reference artifact. The customer's Odoo admin uses this to rebuild equivalent workflows in Odoo Studio using the contact and activity history migrated from Act-On as the reference data.