Migrate from Right On Interactive to Twenty CRM

Right On Interactive contacts migrate to Twenty's Person object as the primary record. All standard fields (name, email, phone, title) map directly. The original contact ID from Right On Interactive is preserved in a custom text field src_record_id__c for reconciliation. Lifecycle stage labels and 3D scoring sub-dimensions migrate as custom fields (see lifecycle and scoring mappings below).

Right On Interactive lifecycle stages are account-configured custom field labels (e.g., Prospect, MQL, Customer, Advocate) that do not map to a fixed platform schema. During discovery we capture the full set of stage labels used in the customer's ROI account, then create a custom Select field in Twenty with matching option values. Stage assignments migrate as the field value on each Person record. We do not enforce any new stage logic; we preserve the labels as named.

The behavioral sub-score from Right On Interactive's 3D model migrates to a custom Number field (behavioral_score__c) on Twenty's Person object. Values transfer as integers or decimals matching the source precision. This field is added to the Person data model before migration begins.

The demographic sub-score from Right On Interactive's 3D model migrates to a custom Number field (demographic_score__c) on Twenty's Person object. Values transfer as integers or decimals matching the source precision. This field is added to the Person data model before migration begins.

The firmographic sub-score from Right On Interactive's 3D model migrates to a custom Number field (firmographic_score__c) on Twenty's Person object. Values transfer as integers or decimals matching the source precision. We also create a composite custom Number field (roi_3d_score_total__c) that stores the sum of all three sub-scores for teams that want a single aggregate view.

Right On Interactive account records with firmographic data migrate to Twenty's Company object. The company name, domain (website), industry, employee count, and annual revenue map to standard Twenty Company fields where available. Additional firmographic properties from ROI that have no direct Twenty equivalent become custom fields on the Company object.

Opportunity data syncing from CRM integrations in Right On Interactive migrates to Twenty's Opportunity object. Deal amount maps to Amount, close date maps to closeDate, deal stage maps to a custom Select field (deal_stage__c) since Twenty does not enforce a fixed stage pipeline schema by default. We create the stage options to match the source deal stages during schema setup.

Right On Interactive campaign records including program assets, budgets, and multi-channel assignments migrate as metadata associations to Person and Company records. Each campaign a contact responded to becomes a Multi-Select tag on the Person record (campaign_tags__c). We do not create a separate Campaign object in Twenty because the current release does not include a native campaign management module; campaign attribution is preserved through tag associations.

Right On Interactive engagement events (email opens, link clicks, form submissions, social interactions) migrate as Activity records linked to the corresponding Person in Twenty. Each engagement type becomes an Activity with type, timestamp, and any associated campaign or asset reference. We resolve the Person record by email match before inserting each Activity. Engagement timestamps are preserved in the Activity's date field.

Right On Interactive call and meeting engagement records migrate to Twenty Activity objects with type set to Call or Meeting, duration stored in a custom number field if applicable, and notes preserved as the activity body. Each Activity links to the Person who was the subject of the engagement. Call disposition and meeting location transfer to custom text fields.

Right On Interactive lead records syncing from CRM integrations migrate to Twenty's Person object. Lead source attribution, initial scoring at time of sync, and any associated company data all transfer to the Person record and its linked Company. We use the Person object as the unified contact container in Twenty rather than splitting into separate Lead and Contact objects.

Event and webinar registrations from Right On Interactive migrate as Activity records with type set to Event Registration. Invitation status, attendance records, and follow-up sequence assignments become custom fields on the Activity. Each Activity links to the registered Person and optionally to the associated Company and Opportunity.