Migrate from Boostr to Microsoft Dynamics 365 Sales

Boostr Advertisers are the buyer accounts in the media sales data model — roughly equivalent to Accounts in Dynamics 365 Sales. We map Advertiser fields (company name, address, billing contact, industry classification) directly to Account. Primary buyer contacts within the Advertiser are extracted as separate Contact records linked to the Account via the primary contact role. If the Advertiser record contains multiple named contacts, we create a Contact per named buyer and set the Account's primary contact by email match.

Boostr Campaigns group multiple Proposals and Orders under a single media campaign umbrella. Dynamics 365 Sales has no native Campaign object at the sales tier (Campaign is a Marketing Cloud concept). We create a custom text field campaign_name__c on the Opportunity and populate it from the Boostr Campaign assignment. If the customer has more than 20 distinct campaigns, we recommend a custom Campaign__c object with a lookup from Opportunity to preserve grouping and enable reporting by campaign.

Boostr Proposals are the draft-offer stage — sent to an advertiser before order confirmation. We map Proposal records to Dynamics 365 Opportunities with a stage value corresponding to a pre-agreed early pipeline stage (Qualification, Proposal/Price Quote, or Negotiation depending on the customer's Boostr stage labels). Proposal-level pricing and line items migrate as Opportunity Product rows or custom fields on the Opportunity. We flag the Proposal-to-Order relationship as a custom field opportunity_parent_proposal__c linking back to the original proposal Opportunity for lifecycle reporting.

Boostr Orders are the booked, confirmed commercial agreements — the transactional record of sold ad inventory. We map Orders to Dynamics 365 Opportunities at the Closed Won stage, preserving the original order number in a custom field order_number__c. The Order-to-Proposal relationship maps to the opportunity_parent_proposal__c lookup on the Opportunity. Revenue figures, billing status, and payment terms migrate directly into the Opportunity amount, closedate, and custom billing fields. If the Order references multiple Proposals, we create a parent Opportunity for the Order and link the Proposal Opportunities as children.

Boostr captures ad inventory as structured line items per Order — placement name, format (display, video, native), flight dates, impressions booked, CPM rate, and unit count. Dynamics 365 Opportunities do not have a native multi-line-item structure beyond the Opportunity Product association, which requires a Pricebook entry. We assess the customer's inventory complexity during scoping: for straightforward setups we create Opportunity Products with custom fields (flight_start__c, flight_end__c, impressions__c, cpm__c); for complex multi-format setups we recommend a custom Ad_Inventory_Item__c object with a lookup to Opportunity and a custom lookup to a Product2 record for pricing.

Boostr tracks revenue at the Order and line-item level with revenue types (guaranteed, non-guaranteed, sponsorship) and billing status. We migrate these directly as Opportunity amount fields (estimated_value__c for estimated, actual_value__c for recognized) and a custom picklist revenue_type__c. For orders with split billing across periods, we create one Opportunity per billing period or use Opportunity Splits if the Dynamics org has that feature enabled.

Boostr's pipeline stages (Prospect, Proposal, Negotiating, Booked, etc.) are configurable per customer. We replicate the customer's stage labels and probability percentages into Dynamics 365 Sales OpportunityStageName and StageProbability fields. Before migration, we coordinate with the customer to confirm which Boostr stages map to which Dynamics stages, and we create a stage mapping document that the Dynamics admin deploys to the target org during schema setup.

Boostr User records (names, roles, team assignments) map to Dynamics 365 Sales User records via name and email lookup. We resolve every Owner referenced on Advertiser, Campaign, Proposal, and Order records against the destination org's User table. Users without a match go into a reconciliation queue for the customer's admin to provision before record import begins. Active/inactive status in Dynamics mirrors the Boostr user active flag.