Migrate from RollWorks Account-Based Platform to Twenty CRM

HubSpot Companies or Salesforce Accounts map directly to Twenty Companies. The domain name from RollWorks Account Lists becomes the Website field on the Twenty Company record. Account List membership is preserved as Tags on the Company record (multiple tags supported via Twenty's tag system). We match Companies by domain during import to avoid duplicates where the same account appears across RollWorks Account Lists and the CRM.

RollWorks Account Lists are collections of target accounts used for campaign targeting and reporting. We extract Account List names and member domain lists, then create corresponding Tags in Twenty (e.g., Tag: 'Q1_Enterprise_List'). The tag assignment is resolved at Company import time by matching domains across list membership files. Account List hierarchy (nested lists) maps to tag parent-child relationships in Twenty where the data model supports it.

Journey Stages in RollWorks are derived from CRM field values synced from Salesforce or HubSpot — they are not a native RollWorks object but a field in the connected CRM. We extract the Journey Stage field definition and recreate it as a custom Select field on the Twenty Company object (e.g., 'icp_fit_tier' or 'abm_journey_stage') with the same picklist values. The field must be created in Settings → Data Model before Company import so that the import CSV can populate it.

HubSpot Contacts or Salesforce Contacts map to Twenty Person records. The Person is created after the parent Company (by domain match) so that the WorkRelations (employment) relationship is satisfied at insert time. Email, name, phone, title, and LinkedIn URL fields map directly. Any contact role data (e.g., decision-maker, champion) stored in the connected CRM maps to a custom Select field on Person.

HubSpot Deals or Salesforce Opportunities map to Twenty Opportunities. The pipeline stage mapping requires configuration in Twenty before import: we create a Stage field on Opportunity with values matching the source dealstage names. Amount, close date, deal name, and probability migrate directly. We resolve the Company (Account) lookup by domain match and the Person (Contact) lookup by email match before Opportunity insert.

RollWorks writes aggregated engagement metrics (ad impressions, clicks, engagement score) back to a custom Salesforce object tied to the Account. This schema is documented in RollWorks help center (AdRoll ABM Data in Salesforce: Custom Objects and Fields). We extract the field names and recreate equivalent custom Number or Currency fields on the Twenty Company object (e.g., adroll_impressions_last_30d, adroll_engagement_score). The Website field on the Salesforce Account is the matching key to resolve Company records.

RollWorks audience segments are built from filter combinations applied to RollWorks' own data and CRM field values. We extract the segment definition (filter criteria, lookback window, included/excluded accounts) as a written document during scoping, then create Tags in Twenty to label records that match the segment membership. Complex segment logic with multiple filter conditions is documented as a filter recipe for manual recreation in Twenty's filter UI.

Sales Insights (Account Spike scoring) are written by RollWorks to the connected CRM as custom fields on the Account or Company record. We map these signal fields to equivalent custom Number fields on Twenty Company (e.g., account_spike_score, intent_signal_strength). The original signal values are preserved so the customer can re-establish their scoring thresholds in Twenty post-migration.

Any custom Salesforce objects or HubSpot custom objects used in the customer's ABM workflow (beyond the AdRoll aggregated data object) migrate to Twenty Custom Objects. We pre-create the destination schema in Settings → Data Model — including field types, picklist values, and lookup relationships — before any CSV import. The customer defines the data model during scoping; we validate field type compatibility (e.g., Salesforce formula fields become read-only or computed fields in Twenty where supported).

Activity history in the connected CRM (Salesforce Tasks/Events or HubSpot engagements) migrates to Twenty as Tasks (for calls, emails, meetings) or Notes (for free-form commentary). We map ActivityDate and body content, and link activities to the resolved Person or Company record by email or domain match. Large engagement histories (over 100,000 records) use chunked CSV import with lookup resolution in batches.