Migrate from Acoustic Campaign to Salesforce Sales Cloud

The primary Acoustic Campaign Database's Contacts map directly to Salesforce Contact records. The contact identifier (email or customer number) becomes the Salesforce ExternalId for dedupe. Email status (active, bounced, unsubscribed) maps to HasOptedOutOfEmail and the Email Bounced flag. Custom fields from the primary Database migrate to custom Contact fields (hs_custom_ prefix) to avoid collision with Salesforce reserved names.

Additional Acoustic Databases that contain company or account-level records split into a Salesforce Account (the organisation) and Contact records. The Database name becomes the Account Name. Relational Table data denormalised onto Contact records joins at the Account level. This prevents duplicate Account creation when the same email appears across multiple Databases.

Each Acoustic Database defines its own field schema (field name, type, required flag). We export the schema definition, translate Acoustic field types to Salesforce equivalents (text to Text, numeric to Number, date to Date), and pre-create all custom fields on the Salesforce Contact object before any record import begins.

Relational Tables hold transactional or behavioural data joined to Contacts via a key. Since Acoustic evaluates these joins server-side at send time and exports only the current membership snapshot (not the join logic), we export the Relational Table rows separately and recreate them as either a Salesforce Custom Object with a Lookup to Contact, or as denormalised custom fields on the Contact record for the most-referenced columns.

Acoustic Queries segment Contacts by filter criteria evaluated at send time. We export the current Query membership as a Contact list snapshot and recreate each Query as a Salesforce Campaign with the matching Contacts as CampaignMembers. The Query criteria themselves (filter logic) are documented separately as a rebuild recommendation for Salesforce Reports or List Views.

Acoustic Programs are multi-step automated message sequences with branching, timers, and conditional logic. We export the Program structure (steps, transitions, branch conditions, timer offsets) as a written journey map. The Program definition does not migrate as Salesforce Flow code because the execution models are structurally incompatible. We deliver a Program inventory document listing each Program's trigger, steps, and recommended Flow equivalent.

Acoustic Mailings (autoresponders, recurring sends, one-off campaigns) migrate as Salesforce Campaign records with the mailing name, subject, sender, and schedule preserved. Historical send performance (send date, open rate, click rate if available) populates Campaign statistics fields. HTML content migrates to Campaign Description or a ContentDocument attached to the Campaign if the customer wants template continuity.

Suppression Lists migrate first in all phases to prevent re-mailing bounced, unsubscribed, or Do Not Email addresses. Opted-out addresses set HasOptedOutOfEmail = true on Contact. Bounced addresses set EmailBouncedReason and EmailBouncedDate. Complaint markers create a Campaign unsubscribe entry for CAN-SPAM and GDPR audit trails. We validate the suppression load before any contact import begins.

Acoustic Web Tracking captures page visits and on-site behaviour tied to Contacts. We export event history as a custom Salesforce object (hs_web_activity__c) with fields for page URL, event timestamp, session ID, and Contact lookup. Alternatively, we map behavioural events to Salesforce Tasks if the customer prefers a native object without a custom schema.

Acoustic email templates and content blocks export as HTML. Acoustic personalisation tags ($contact.field$) translate to Salesforce merge field syntax ({!Contact.field}). We preserve the template structure in a ContentDocument record and deliver a tag-translation matrix so the customer's admin can reassemble templates in Salesforce Classic or Lightning Email Templates.

Cross-channel campaign metadata (schedule, audience, content) migrates as Campaign records. The underlying messaging provider credentials (Twilio, WhatsApp Business API) do not carry across; we document the channel configuration requirements and the customer configures new credentials in Salesforce or their preferred channel platform. Active SMS opt-in status migrates to Contact custom fields.

Acoustic Campaign user records referenced on Contacts, Programs, and Mailings map to Salesforce User records by email match. We resolve each Acoustic Owner ID to the corresponding Salesforce User ID during import. Any Acoustic Owner without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

The Acoustic Email Activities related list (used in Person Account integrations) migrates as Salesforce EmailMessage records linked to the Contact. Each email send event becomes an EmailMessage with Subject, TextBody, HtmlBody, Status, and MessageDate. Open and click tracking events map to Task records with custom fields for the engagement type.

Acoustic's contact key (typically email or a numeric customer identifier) becomes the Salesforce Contact.External_System_Id__c custom field used as an external ID for dedupe. If the Acoustic Database uses a composite key or a non-email identifier, we use that value as the external ID and map email separately to Contact.Email.