Migrate your Boostr data

Advertisers are the buyer accounts in Boostr's media data model, roughly equivalent to Companies/Accounts in a standard CRM. We map Advertiser fields to the destination's account object and preserve advertiser-level custom properties as mapped custom fields.

Boostr Campaigns group multiple proposals and orders under a single media campaign umbrella. We preserve Campaign-to-Proposal relationships and map Campaign metadata into the destination's equivalent grouping structure or tag system.

Proposals are a distinct stage object representing an offer sent to an advertiser before an order is confirmed. We treat Proposals as a conditional Deal state and preserve proposal-line-item pricing, terms, and product associations during migration.

Orders are the booked, confirmed commercial agreements — the core transactional record in Boostr's OMS. We map Orders to Deals in standard CRMs but note that the line-item structure (Ad Units × Placements × Dates) may require flattening into a Deal-level record with custom fields for destination platforms that lack an OMS.

Ad Inventory represents the sellable units (placements, impressions, formats) attached to an Order. These map to custom line-item or product records in most destination CRMs. We extract inventory metadata (placement, format, CPM, impressions) and reconstruct it as structured custom fields.

Boostr tracks revenue at the order and line-item level. Revenue figures, revenue types, and billing status are standard fields that we migrate directly into the destination's deal monetary fields or a dedicated revenue custom object.

Boostr's pipeline stages (Prospect, Proposal, Negotiating, Booked, etc.) are configurable but follow a standard media sales lifecycle. We replicate the customer's stage labels and probabilities into the destination CRM's pipeline configuration.

User records including names, roles, and team assignments map to the destination's user or owner object. We perform a name-and-email lookup to avoid duplicate user creation when the destination already has matching accounts.

Boostr supports custom fields on Advertisers, Campaigns, Orders, and other objects. We discover the full custom field schema during scoping and apply field-level mapping to the destination's corresponding custom field infrastructure.

Boostr's GAM integration and other connected apps are platform-specific OAuth connections that cannot be replicated in a destination system. We document the integrations in the migration audit and advise the customer to re-establish them post-migration.