Migrate from Boostr to Twenty CRM

Boostr Advertisers map directly to Twenty Companies. The Advertiser name becomes the Company name; domain and website fields map from Boostr's advertiser website field. We set a custom field advertiser_type__c or a Company type label to 'Media Advertiser' to preserve the media-industry context for segmentation. All custom fields on the Advertiser object map to Twenty custom fields on Company.

Boostr Campaigns group multiple Proposals and Orders under a single media campaign umbrella. We map Campaign records to a Twenty Custom Object named Campaign with a name, status, and date range fields. If the customer prefers a flat model, Campaign metadata (name, start/end dates, budget) migrates as custom fields on each related Opportunity. The relationship between Campaign and the Proposals/Orders that belong to it is preserved via a lookup field on the Opportunity.

Boostr Proposals represent draft offers sent to an advertiser before order confirmation. We map these to Twenty Opportunities with a pipeline stage labeled 'Proposal' or 'Pending' and a custom status field proposal_status__c set to 'Proposal'. Proposal line-item pricing, terms, and valid-until dates migrate as custom fields on the Opportunity. The Proposal-to-Order lineage is preserved by linking the Proposal Opportunity to the resulting Order Opportunity via a custom lookup field related_order__c.

Boostr Orders are the booked, confirmed commercial agreements — the core transactional record in Boostr's OMS. We map Orders to Twenty Opportunities with the pipeline stage set to Closed Won. Order total revenue maps to Opportunity amount; billing status and payment terms migrate as custom fields. The Order-to-Proposal relationship (if the Order originated from a Proposal) is preserved via the related_proposal__c lookup field.

Boostr captures ad inventory as structured line items per Order — placement, format, dates, impressions, CPM, and unit count. Each line item becomes a separate Custom Object record of type Ad Unit linked to the parent Opportunity via a lookup. Fields include placement__c, format__c, start_date__c, end_date__c, impressions__c, cpm__c, and unit_count__c. This structure preserves the granular inventory data that a flat Opportunity record would lose.

Boostr tracks revenue at the Order and line-item level with revenue types and billing status. We map Order revenue figures directly to the Opportunity amount field. For line-item-level revenue, we aggregate into a custom revenue field on the Ad Unit custom object or a custom total_revenue__c field on the Opportunity. Billing status (invoiced, paid, pending) migrates as a picklist field on the Opportunity.

Boostr's configurable pipeline stages (Prospect, Proposal, Negotiating, Booked, etc.) map to Twenty pipeline stages. We replicate the customer's stage labels into Twenty's pipeline configuration, setting stage probabilities to match Boostr's configured values. Boostr's Proposals map to the Proposal/Pending stage; Orders map to Closed Won.

User records from Boostr — names, roles, team assignments — map to Twenty Workspace Members. We perform a name-and-email lookup against the Twenty destination workspace before import. Any Boostr Owner without a matching Twenty Member is flagged in the reconciliation report for the customer's admin to provision. Important: Twenty requires workspace members to exist before importing records that reference them, so we handle user provisioning before record import.

Boostr supports custom fields on Advertisers, Campaigns, Orders, and other objects. We discover the full custom field schema during scoping, create matching custom fields in Twenty's Settings → Data Model before import, and map each field by type. Text, number, date, and picklist fields migrate directly; multi-select picklists in Boostr require a custom field type in Twenty with equivalent options. Custom field schema must be created before CSV import because Twenty's import creates records, not fields.

Boostr's GAM integration and other connected apps use platform-specific OAuth connections that cannot be replicated in Twenty CRM. We document all active integrations during discovery and include a reconnection checklist in the post-migration handoff. The customer must re-authenticate Boostr's GAM OAuth connection (if applicable) and any other connected apps in their Twenty workspace settings after migration. This is a configuration step, not a data migration step.