Migrate from Boostr to Nutshell

Boostr Advertisers map directly to Nutshell Accounts. Advertiser name becomes Account Name; domain and billing address map to the corresponding Account fields. Advertiser-level custom fields (industry classification, advertiser tier, primary contact name) map to Nutshell custom fields on Account. The Advertiser-to-Account mapping is the first data load because all downstream objects (Orders, Campaigns) reference it.

Boostr Campaigns group multiple Proposals and Orders under a single media campaign umbrella. Nutshell does not have a native Campaign object equivalent to the CRM Account object. We map Campaign metadata (campaign name, start/end dates, channel, budget) into Nutshell custom fields on the linked Account and Opportunity, and create a Nutshell Pipeline named for the Boostr Campaign grouping structure so that Opportunities can be filtered by campaign context.

Boostr Proposals in draft or pending status — sent to an advertiser but not yet confirmed — map to Nutshell Leads. The Proposal Line Item pricing, placement details, and CPM data flatten into Nutshell custom fields on the Lead record. We preserve the original Boostr Proposal ID in a custom field boostr_proposal_id__c for audit trail. This split ensures draft media deals are not mixed with confirmed bookings in Nutshell's Opportunity pipeline.

Boostr Orders — confirmed commercial agreements with booked inventory — map to Nutshell Opportunities in a Closed Won stage. Order fields (order date, total value, billing status) map to Opportunity fields (Close Date, Amount, Stage). The Order-to-Opportunity mapping preserves the full closed-won commercial record that represents actual revenue in the media sales pipeline.

Boostr captures ad inventory as structured line items per Order — placement name, format type, run dates, impression volume, CPM rate, and unit count. Nutshell has no native line-item or product-schedule sub-record on Opportunities. We extract each line item as a separate custom field set (placement_1, format_1, impressions_1, cpm_1, and so on) on the Opportunity. For Orders with more than five line items, we recommend consolidating to the top five by revenue and noting the remainder in a summary custom field.

Boostr revenue figures tracked at the Order and line-item level map directly to Nutshell Opportunity Amount fields. Revenue type (direct, programmatic, sponsorship) and billing status map to Nutshell custom fields on the Opportunity. Revenue records represent the financial summary of closed orders and must land in Nutshell before pipeline reporting is meaningful.

Boostr User records — names, roles, team assignments — map to Nutshell Users. We resolve owners by email match across both platforms. Any Boostr Owner without a matching Nutshell User goes into a reconciliation queue for the customer's Nutshell admin to provision before record import resumes. Owner resolution must complete before any record with an Owner assignment can be imported.

Boostr supports custom fields on Advertisers, Campaigns, Orders, and other objects. We discover the full custom field schema during scoping and map each to the equivalent Nutshell custom field on Account (for Advertiser-level properties), Lead (for Proposal-level properties), or Opportunity (for Order-level properties). Nutshell supports custom fields on People, Companies, and Leads — not on Opportunities directly, so Order-level custom fields attach to the linked Opportunity's related Account or into a designated custom fields section if Nutshell's current product version supports Opportunity-level custom fields.

Boostr email logging (limited to basic activity capture due to Boostr's restricted Gmail integration) migrates to Nutshell Emails linked to the associated Account, Person, or Lead. Email content migrates as a Nutshell Email record; the timestamp and sender/recipient map to standard Nutshell fields. Any Boostr engagement notes attached to emails migrate as Notes linked to the same record.

Boostr call records (manual or from any connected dialer) migrate to Nutshell Call records linked to the associated Account, Person, or Lead. Call duration and disposition migrate to Nutshell Call fields. Nutshell's API supports Call import, but CSV import does not support Calls; we use the Nutshell API directly for this object.

Boostr Notes attached to Advertisers, Proposals, or Orders migrate to Nutshell Notes linked to the corresponding Account, Lead, or Opportunity. Note body, author, and timestamp migrate directly. We preserve the Boostr note ID in a custom field for reconciliation.