Migrate from Acoustic Campaign to Pipedrive

Acoustic Campaign Contacts map directly to Pipedrive People. Email address is the dedupe key. We apply a suppression-status check before inserting each Person: if the email appears on the Acoustic Suppression List, HasOptedOutOfEmail is set to true in Pipedrive. Custom Contact fields from the source Database schema map to custom fields on the Person record, respecting Pipedrive's field-type constraints per plan tier.

Each Acoustic Campaign Database becomes a Pipedrive Organization. The Database name maps to Organization.name. If the same company appears across multiple Databases (common when teams share contact records), we create one Organization and attach all matching People, noting the cross-Database provenance in a custom field db_origin__c for audit. Schema custom fields unique to one Database map as custom fields on Organization.

Relational Tables hold transactional or behavioural data joined to Contacts via a key. The join logic evaluates at send time in Acoustic and is not exportable as a filter definition. We export the Relational Table rows separately, denormalise the most-referenced fields onto each Contact record as custom Person fields, and import the full table as a Pipedrive custom object with a foreign-key lookup to Person where the customer requires the relational model preserved.

Acoustic Queries segment Contacts using Relational Table joins and contact property filters evaluated at send time. The current snapshot of Query membership (the list of Contact IDs meeting the Query criteria at export time) migrates as a static Pipedrive list. The original Query filter logic is not transferable; we document the filter conditions in a written segment inventory for the customer to recreate as Pipedrive filters.

Acoustic Campaign Suppression Lists hold opted-out, bounced, and Do Not Email addresses. We migrate all suppression entries before any Contact import. For each suppressed email, we set Pipedrive HasOptedOutOfEmail = true on the matching Person record. If the Person does not yet exist in Pipedrive, the suppressed address is added to a blocked-address list for reference. This sequencing prevents re-mailing previously opted-out addresses on first send.

Acoustic Programs are multi-step automated message sequences with branching, timers, and conditional logic across email and SMS. Pipedrive does not have a native journey-orchestration engine. We do not migrate Programs as automation code. We deliver a written inventory of every active Program with its trigger conditions, steps, branching logic, and timer settings, plus a recommended Pipedrive Workflow equivalent for the customer's admin to rebuild.

Acoustic Mailings are individual sends or recurring campaigns with HTML content, subject, sender, and schedule. We export Mailing HTML content as plain text assets for the customer to repurpose. Acoustic personalisation tags ($contact.field$ syntax) are documented and translated to a reference sheet for Liquid or Handlebars syntax in Pipedrive-connected tools. The send history (send date, open rate, click rate) does not migrate as Pipedrive has no mailing analytics object.

Acoustic email templates and content blocks export as HTML. Acoustic-specific personalisation tags ($contact.field$) are documented in a translation reference. Pipedrive's email templates use plain text and limited HTML; we import the content and flag any tags requiring manual conversion for the customer's email integration tool.

If Acoustic Campaign is used with a CRM connector that tracks deals or opportunities, those records migrate to Pipedrive Deals. Acoustic deal-stage values map to Pipedrive Stage values per a customer-approved stage matrix created before migration. The Deal's linked Person or Organization resolves via the Contact-to-Person mapping.

Acoustic Campaign users referenced on Contacts and Programs map to Pipedrive User records by email match. Owners without a matching Pipedrive User are held in a reconciliation queue for the customer's admin to provision before record import resumes.

Acoustic engagement history (calls, meetings, notes) migrates to Pipedrive Activities of the matching type. Activity timestamps preserve from the source record. Call duration migrates to Pipedrive's duration field where supported. Note body migrates to the Pipedrive note field linked to the Person or Organization.

Acoustic web tracking events capture on-site behaviour tied to Contacts. Pipedrive does not have a native behavioural tracking or CDP object. We export the web tracking event data as a CSV for the customer's analytics team to load into a separate tool if required. This is documented in the written handoff rather than executed as part of the CRM migration scope.