Migrate from RollWorks Account-Based Platform to Odoo CRM

RollWorks Account Lists map to Odoo Contact records. Each Account List is extracted with its full member list (Account name, domain, and any CRM-synced fields). We map Account List membership to Odoo Tags using the res.partner.tag model, creating one tag per Account List and applying it to all contacts in that list. If Account Lists contain sub-lists, we flatten the hierarchy into a parent-tag and child-tags structure. The Odoo Contact's email, phone, address, and company name fields are populated from the CRM sync source. Dedup key is email domain for B2B contacts.

RollWorks Account Groups (collections of Account Lists) map to Odoo Contact Groups or a custom res.partner.group model depending on the customer's Odoo edition. We extract the full group hierarchy and apply it as a nested tag structure in Odoo. Groups that reference multiple Account Lists produce multiple tag assignments on the same Contact. If the customer uses Odoo CRM's native grouping by Sales Team, we map Account Groups to Odoo Sales Team assignments on the Contact record.

RollWorks Journey Stages are derived from CRM field values ingested through the Salesforce or HubSpot integration and do not have a native Odoo equivalent. We create a custom Char or Selection field on res.partner (odoo_crm_journey_stage__c) and populate it with the Journey Stage value from the CRM sync source. If the customer uses Odoo CRM pipelines, we map Journey Stages to Odoo CRM stage assignments on linked Opportunities where applicable. The original stage source field in Salesforce or HubSpot is preserved in the mapping documentation.

RollWorks Hot Contacts (deanonymized web visitors) are pushed to the connected CRM as leads or contacts via workflow actions and migrate as Odoo Contact records. We extract the full contact profile from the CRM sync source including any custom fields, and apply the corresponding Odoo tags based on the RollWorks Hot Contact designation. Email, phone, address, company name, and contact owner map directly to Odoo res.partner fields. Note that Lead records in RollWorks cannot be associated to Accounts in Journey Events, so teams using Leads over Contacts may have attribution gaps that we flag during scoping.

Company records from the connected Salesforce or HubSpot CRM sync map to Odoo Company records (res.partner with is_company=True). Company name, website, industry, employee count, and address fields map to the corresponding Odoo fields. The RollWorks Account name becomes the Odoo Company name. We use company domain as the dedupe key during import. Company-level engagement scores from RollWorks (if available in the CRM sync) migrate to custom fields on the Odoo Company record.

RollWorks Account Spike scores and Sales Insights are written to Salesforce or HubSpot widgets and do not have a native Odoo equivalent. We create custom Float or Integer fields on res.partner (spike_score__c and engagement_rank__c) and populate them from the CRM sync source if the connected platform carries these values. If the CRM sync does not expose these scores directly, we document them as unavailable for automated migration and recommend that the customer's admin rebuilds scoring logic in Odoo using Odoo Automations or a third-party lead scoring app.

RollWorks creates custom Salesforce objects and fields to store aggregated advertising engagement data. We audit the customer's Salesforce schema during scoping to identify these custom objects, then replicate the field schema as custom fields on the Odoo res.partner record. AdRoll aggregated metrics (impressions, clicks, engagement rate per account) are stored as Float or Integer custom fields on the Odoo Company or Contact. Any rollup summaries are recalculated in Odoo after migration using Odoo computed fields if the aggregation logic is required.

RollWorks Workflows (Triggers and Actions) are defined in the AdRoll ABM orchestration layer, not in the connected CRM. We perform a dedicated extraction pass to capture workflow definitions (trigger type, conditions, actions, target CRM updates). Odoo Automations use a different trigger model (based on Odoo models and on_change events rather than advertising event triggers), so Workflows cannot be migrated as code. We deliver a written inventory of every active RollWorks Workflow with its trigger, conditions, and actions mapped to a recommended Odoo Automation equivalent. The customer's admin rebuilds them in Odoo Studio post-migration.

RollWorks Journey Events aggregate advertising engagement and G2 buyer intent signals and associate them with CRM Contacts. Odoo has no native Journey Events model. We extract Journey Event summaries from the CRM sync source where available (typically as custom Salesforce fields or HubSpot properties) and migrate them as custom fields on the Odoo Contact or Company. Live Journey Event streaming cannot be replicated in Odoo without a third-party ABM integration app. We document the gap and recommend Odoo Marketing Automation or a third-party ABM tool as a replacement for ongoing Journey Event ingestion.

RollWorks campaign structure (campaign names, audience targeting rules, channel assignments) lives in the advertising layer and does not have a native Odoo equivalent. We extract campaign configuration and audience rules and store them in a CSV inventory document that the customer's admin uses to configure Odoo CRM Campaigns or a project module if campaign tracking is required. Live ad creative assets, active ad spend data, and dynamic CPM metrics do not migrate. We preserve the raw impression and spend data from the CRM sync in a CSV for post-migration cost-per-action calculation if needed.

RollWorks Owners (users assigned to Account Lists, Contacts, and Workflows) map to Odoo Users. We resolve Owners by email match against the Odoo destination database. Any RollWorks Owner without a matching Odoo User is placed in a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignments on migrated Contacts map to Odoo's user_id field on res.partner.

RollWorks Audience Segments are built from the platform's own data and CRM field combinations. We document every active segmentation rule used in RollWorks campaigns and translate them into Odoo Tags and saved filter views. Segments built from CRM field combinations map to Odoo saved searches using the same field criteria. Segments built from RollWorks proprietary data (intent signals, firmographic scoring) cannot be replicated automatically and are documented for the admin to rebuild using Odoo Automations or a third-party enrichment tool.