Migrate from Boostr to HubSpot

Boostr Advertiser is the account-level entity. We map it to HubSpot Company directly. Boostr advertiser properties (industry, website, annual revenue) map to HubSpot's standard Company fields. Any Boostr custom advertiser fields migrate as HubSpot custom properties on Company as required.

Boostr Contact migrates to HubSpot Contact 1:1. Standard fields (name, email, phone, job title) map directly. Boostr contact owner resolves by email match against HubSpot users. Boostr contact associations to Advertisers map to HubSpot's Company-Contact association and preserve historical data.

Boostr Campaign is the deal-equivalent entity. We map it to a HubSpot Deal inside a dedicated 'Boostr Campaigns' pipeline. Campaign name becomes Deal name; campaign status maps to HubSpot pipeline stage values. We preserve campaign-level metadata (campaign type, start/end dates, total budget) as custom deal properties.

Boostr Line Items map to HubSpot Deal Line Items. Each line item's product name, quantity, unit price, and total amount migrate as HubSpot Line Item fields. Boostr's CPM/CPC rate fields become custom properties on the HubSpot Line Item. Line items are linked to the parent HubSpot Deal representing the campaign.

Boostr products (ad placements, inventory units) map to HubSpot Products. Product name, description, unit price, and cost migrate as HubSpot Product fields. If Boostr uses a price list structure, we import it as a HubSpot product library and associate price books if multiple price lists exist.

Boostr deal stage values map to corresponding HubSpot pipeline stages. We preserve the stage probability percentage as a custom property on the Deal. If Boostr uses weighted probability by stage, we apply those weights to HubSpot stage-level forecast categories accurately.

Boostr owner records resolve by email match to HubSpot users. Any Boostr owner who does not have a corresponding HubSpot user is flagged before migration; you either create the HubSpot user first or assign those records to a designated fallback owner.

Boostr notes and tasks migrate as HubSpot engagements. Note body maps to HubSpot Note; task subject, due date, and status map to HubSpot Task. Original timestamps and owner IDs are preserved. Emails and calls logged in Boostr migrate as HubSpot email and call engagements.

Any Boostr custom fields on Advertiser that have no HubSpot standard equivalent become HubSpot custom properties on Company. We create the property in HubSpot (with appropriate type — text, number, date, picklist) before the migration run. You review and confirm property names in the migration plan.

Boostr campaign-level custom fields migrate as HubSpot Deal custom properties. Field type conversion follows HubSpot's supported types. Multi-select picklists from Boostr map to HubSpot multi-checkbox or single-select properties depending on the source values and ensure data integrity across the migration.

Boostr workflows and automations (50+ per G2 review) do not migrate. They must be rebuilt in HubSpot using HubSpot's workflow builder, automation sequences, or HubSpot Operations Hub. We export your Boostr workflow definitions as a reference document for your HubSpot admin to use during rebuild.

Boostr's pre-built media-specific dashboards (best practice dashboards per boostr.com) do not migrate. The underlying deal, line item, and company data does migrate into HubSpot — your team can then rebuild reports using HubSpot's native reporting or connect to a BI tool. The data underpinning the reports is fully preserved.