Migrate from Boostr to Freshsales

Boostr Advertisers map to Freshsales Accounts. Advertiser name maps to Account name, and the primary contact's email or phone maps to the account's phone or website field. We use Advertiser ID as the external reference for dedupe logic during import. This is the first object we import because Account records are the parent of most other objects in Freshsales and satisfy required lookups during subsequent imports.

Boostr Campaigns group multiple Proposals and Orders under a single media campaign umbrella. We map Campaigns to Freshsales Deals with a custom field boostr_campaign_name__c carrying the original Campaign name. If a Campaign contains multiple Orders, we create one Deal per Order but tie them by populating boostr_campaign_name__c so reports can roll up by Campaign. Campaign-level revenue and date metadata migrate as fields on each related Deal.

Boostr Proposals are the pre-booking offer state with no confirmed commercial agreement. We map Proposals to Freshsales Deals in a draft or pending stage status — the stage name is configured in Freshsales during schema setup to match the customer's Boostr Proposal workflow labels. Proposal line items (pricing, quantities, formats) migrate as custom fields on the Deal record because Freshsales Deals do not have native line-item sub-objects.

Boostr Orders are confirmed, booked commercial agreements — the transactional record in Boostr's OMS. We map Orders to Freshsales Deals in a closed-won or booked stage. The Order's billing status, total value, and revenue type map to Deal monetary fields and a custom status field. The Proposal-to-Order lineage is preserved by linking the Deal's custom boostr_proposal_id__c field to the migrated Proposal Deal, enabling the customer to trace the full lifecycle from offer to booking.

Boostr captures ad inventory as structured line items per Order — placement, format, dates, impressions, CPM, and unit count. Freshsales does not have native deal line items. We recommend a Freshsales Custom Module (available on Pro and Enterprise plans) named Ad Units with fields matching the inventory schema: Placement, Format, StartDate, EndDate, Impressions, CPM, and UnitCount. Each Ad Unit record links to the parent Order Deal via a lookup relationship. If the customer is on the Free plan without custom modules, we flatten the primary line item into named Deal custom fields and document the remaining units in the mapping spec.

Boostr tracks revenue at the Order and line-item level. Revenue figures, revenue type, and billing status migrate directly into Freshsales Deal monetary fields (amount, expected close date) and a custom boostr_revenue_type__c field. Line-item revenue aggregates into the parent Order Deal's amount field.

Boostr's pipeline stages (Prospect, Proposal, Negotiating, Booked, etc.) are configurable per customer. We replicate the customer's exact stage labels into Freshsales Deal stages during schema setup. Stage probabilities migrate to the corresponding Freshsales stage weights. The Proposal-to-Order lifecycle is mapped to the stage sequence: Proposal maps to a pre-confirmation stage, Order maps to the closed-won or booked stage.

Boostr User records (names, roles, team assignments) map to Freshsales User records. We perform an email-based lookup to match Boostr owners to existing Freshsales users and avoid creating duplicate users. Any Boostr user without a matching Freshsales account enters a reconciliation queue for the customer's admin to provision before record import resumes.

Boostr supports custom fields on Advertisers, Campaigns, Orders, and other objects. We discover the full custom field schema during scoping, map each to a corresponding Freshsales field (using Freshsales's custom field types on Contacts, Accounts, Deals, and custom modules), and apply type conversion where needed (Boostr date fields to Freshsales date fields, multi-select to Freshsales multi-select picklists).