Migrate from Boostr to Odoo CRM

Boostr Advertisers (the buyer account record) map to both an Odoo Contact and a corresponding Odoo Company (Address) record. The Advertiser name becomes the Company name; the primary contact name and email become the Contact. We extract Advertiser custom fields (industry, agency relationship, primary contact role) into Odoo Contact custom fields. Multi-contact Advertisers result in one primary Contact linked to the Company with additional Contacts as related Odoo Contacts under the same Company.

Boostr Campaigns (grouping multiple Proposals and Orders under one media campaign umbrella) map to Odoo CRM Opportunities with a custom field boostr_campaign_id__c and boostr_campaign_name__c preserved for lineage. If the customer uses Odoo Project for campaign project management, we map Campaign to Project and link Opportunities to the Project as deliverables. The customer chooses the strategy during scoping based on whether they track media campaigns as sales pipeline records or as project delivery records.

Boostr Proposals (draft offers before order confirmation) map to Odoo CRM Opportunities with Stage set to a configured draft state (Proposal Sent or Negotiation) that mirrors Boostr's proposal lifecycle. Proposal-level pricing, advertiser references, and line items migrate to Opportunity custom fields or Opportunity Product Lines. The original Boostr proposal ID is preserved in boostr_proposal_id__c on the Opportunity record.

Boostr Orders (confirmed commercial bookings) map to Odoo CRM Opportunities with Stage set to Won and Expected Revenue populated from the Order total value. Order-to-Proposal lineage is preserved by linking the Odoo Opportunity (Won) to the parent Odoo Opportunity (Proposal) via a custom lookup field. Order revenue type and billing status migrate to custom fields.

Boostr Ad Inventory Units (placement, format, dates, impressions, CPM, unit count) attached to each Order are extracted as separate rows during transformation. Each line item becomes an Odoo Opportunity Product Line entry with custom fields boostr_placement__c, boostr_format__c, boostr_impressions__c, boostr_cpm__c, and boostr_start_date__c, boostr_end_date__c. If Odoo Inventory is in use, we recommend creating a Product record per ad format for deeper tracking.

Boostr revenue figures at the Order level migrate to Odoo Opportunity Expected Revenue. If the customer uses Odoo Accounting alongside CRM, we create corresponding Account Move entries in draft state for the customer's accounting team to review and post. Revenue type (CPM, flat-rate, hybrid) and billing status migrate to custom fields on the Opportunity.

Boostr's configurable pipeline stages (Prospect, Proposal, Negotiating, Booked, etc.) map to Odoo CRM Stage records. We replicate the customer's stage labels and probabilities into Odoo Stages, setting the probability percentages per Boostr's configured values. Won and Lost stages map directly.

Boostr User records (names, roles, team assignments) map to Odoo User. We resolve by email match during import. Any Boostr Owner without a matching Odoo User is held in a reconciliation queue for the customer's admin to provision. Odoo's multi-company configuration requires us to map Boostr team assignments to Odoo company or workspace records during user provisioning.

Boostr custom fields on Advertisers migrate to Odoo Contact custom fields. We discover the full custom field schema during scoping and apply field-level mapping. Odoo Studio allows admin-level custom field creation without developer access, which we use to pre-provision the schema before migration.

Boostr custom fields on Orders migrate to Odoo Opportunity custom fields. Custom field types (text, number, date, selection) map to equivalent Odoo field types. Selection fields with restricted values must have the same picklist values defined in Odoo before import to avoid rejection.

Boostr's Google Ad Manager push integration uses platform-bound OAuth tokens that cannot be replicated in Odoo. We document the active GAM connection details (publisher account ID, network code, order setup) during discovery and include a reconnection checklist in the post-migration handoff. The customer's ad ops team re-establishes the GAM connection in their ad serving stack as a configuration step, not a data migration task.

Boostr's 50+ out-of-the-box media-specific workflows (proposal generation, order confirmation, GAM push, revenue recognition) are platform-bound and do not migrate. We deliver a written inventory of every active Boostr workflow with its trigger, conditions, actions, and recommended Odoo Automated Actions equivalent. Odoo uses Server Actions and Automated Actions (available from Odoo Standard) as the rebuild target.