Migrate from Acoustic Campaign to HubSpot

Each Acoustic Campaign database exports contact rows. We map every contact to a HubSpot Contact record, preserving the original email, phone, name, and all standard system fields. Custom fields on the contact become HubSpot custom properties with matching data types.

Acoustic databases contain a separate lead entity alongside contacts. We merge these into HubSpot Contacts, flagging the original entity type as a custom property (Original_Entity_Type__c) for audit and reporting continuity. If your team uses HubSpot's separate Lead object, we can split by a lifecycle stage criteria instead.

Acoustic Campaign stores organization data as columns within contact databases. We extract unique organization names and domains, create HubSpot Company records, and link them back to the corresponding contacts via the primary company association. Secondary company affiliations from Acoustic require HubSpot Account Contact Relationships.

Acoustic lists are named collections of contacts filtered by query rules. We map each list to either a HubSpot static list (explicit contact collection) or a HubSpot active list (filter-based smart list) depending on whether the original list used fixed inclusions or dynamic query criteria. List names are preserved as-is.

Acoustic Campaign custom fields are database columns holding values specific to each contact. We create corresponding HubSpot custom properties on the Contact object, matching field types (text, number, date, picklist, checkbox). Picklist values require explicit value-by-value mapping if the options differ between platforms, ensuring data integrity across the migration.

Acoustic Campaign assigns a numeric contact key to each record. We store this as the native HubSpot object ID for traceability and to support delta-run de-duplication if a second migration pass is needed after go-live on the HubSpot platform.

Acoustic tracks sends, opens, clicks, and unsubscribes per contact per campaign. We attach these as engagement records to the HubSpot Contact timeline with the original timestamp, campaign name, and action type. Bounce events are logged as engagement notes for deliverability reporting.

Acoustic programs and multi-step automation flows have no direct HubSpot equivalent. We export your program definitions (trigger types, steps, conditions, delays) as a structured JSON reference document your team can use to rebuild logic in HubSpot's workflow builder. The automation data itself does not migrate.

Acoustic suppression lists contain contacts excluded from sends. We import these as HubSpot static lists and flag the contacts with a suppress-from-marketing property. HubSpot's native unsubscribe mechanism handles compliance, but the suppression list history is preserved for audit trail and compliance verification.

Acoustic Campaign stores SMS subscribers as contacts with phone numbers and opt-in status. We map these to HubSpot contacts, preserving the phone number and SMS consent flag as a custom property (SMS_Opt_In__c). HubSpot's SMS consent model uses the contact's communicationSubscribe property.

HubSpot's Createdate is set at import time by design. We preserve the original Acoustic Campaign record creation timestamp as a custom datetime property (Original_Create_Date__c) for reporting continuity. This is critical for teams that track account tenure or report against historical create dates.

Acoustic Campaign stores owner IDs as numeric values. We resolve these by email match against HubSpot users. Unresolved owners are flagged before migration; your team either creates HubSpot user accounts or assigns those records to a fallback owner during the migration run.