Migrate your Acoustic Campaign data

Contacts are the primary subscriber record within a Database. Each Contact has a unique identifier (typically email or customer number), system fields (email status, opt-in date), and custom fields defined per Database. We migrate Contacts via XML or REST API preserving the unique identifier and all custom field values.

Databases are top-level Contact containers — an account can have many. Schema (fields, types, required flags) is defined per Database. We export each Database independently and map its schema to one or more destination lists, flagging multi-Database accounts during scoping because most destination ESPs use a single contact pool.

Relational Tables hold transactional or behavioural data joined to Contacts via a key. Queries can reference these joins for segmentation. We export the Relational Table rows and recreate them as either custom objects (Salesforce Marketing Cloud, Braze) or denormalised attributes on the Contact (most other ESPs).

Queries are saved filter definitions over Contacts plus Relational Table joins. The filter logic is evaluated at send time. We export the current Contact membership of each Query as a snapshot list and document the original filter so the customer can rebuild the dynamic logic in the destination's segmentation engine.

Programs are multi-step automated message sequences with branching, timers, and conditional logic. Active enrollments and historical completion state are exported via the API. The Program structure itself is rebuilt in the destination journey builder, as cross-platform automation logic does not transfer one-to-one.

Mailings are individual sends — autoresponders, recurring sends, or one-off campaigns. We migrate Mailing metadata (name, subject, sender, schedule) and the HTML content where the customer wants prior campaigns visible in the destination history. Send statistics typically stay in the source as reporting data.

Suppression Lists hold opt-outs, bounces, and Do Not Email markers. We migrate the suppression entries ahead of any Contact import to ensure the destination ESP does not re-mail addresses that should remain suppressed under CAN-SPAM and GDPR obligations.

Web Tracking captures page visits and on-site behaviour tied back to Contacts. We export event history where the customer wants behavioural continuity in the destination, mapped to the destination's event ingestion endpoint (Customer.io, Iterable, Braze) or denormalised onto Contact records as last-event attributes.

Email templates and reusable content blocks are exported as HTML. Acoustic-specific personalisation tags ($contact.field$ syntax) are translated to the destination's tag syntax (Liquid, Handlebars, or the destination's proprietary format) during import.

Cross-channel campaigns export with their schedule, audience, and content. The underlying messaging provider integration (Twilio, vendor-specific WhatsApp API) does not carry across — credentials and provider linkage are re-established in the destination platform during cutover.