Migrate from Acoustic Campaign to HighLevel

Acoustic Campaign Contacts inside a Database map directly to GoHighLevel Contacts. Each Database is processed independently and imported into GoHighLevel as a separate batch with tags identifying the source Database name. Email address is the dedupe key. Custom fields defined in the Database schema are pre-created in GoHighLevel before import so field mapping is 1:1 at runtime.

When an account uses multiple Databases with distinct schemas, each Database's Contacts import into GoHighLevel with a tag naming the source Database. For each Database with unique custom fields, we create a corresponding Custom Field group in GoHighLevel. If the same email appears across multiple Databases, the most recently modified record wins and the earlier records are flagged for review.

Relational Tables hold transactional or behavioural rows joined to Contacts via a key field. We export the Relational Table rows and recreate them as GoHighLevel Custom Object records. Each record links back to the parent Contact via a Custom Object relationship field. Acoustic's server-side join evaluation means the join logic does not carry; the customer decides whether to recreate the equivalent segment logic using GoHighLevel Workflow conditions or tags.

Acoustic Queries are saved filter definitions that evaluate at send time against current Contact state. We export the current Contact membership of each Query as a snapshot list and import those Contacts into GoHighLevel with a tag matching the Query name. The filter criteria are documented in the handoff document for the customer to rebuild as GoHighLevel Workflow triggers or Smart List conditions.

Acoustic Programs with active enrollments are documented in full detail including trigger type, branch conditions, delay timers, and message actions. Programs cannot migrate as executable code because GoHighLevel Workflows use a different trigger-action model. We deliver a Program-to-Workflow translation document for each active Program, and the customer or a GoHighLevel specialist rebuilds them post-migration.

Acoustic Mailings (autoresponders, recurring, one-off) migrate as Campaign records with subject, sender, schedule, and HTML content. GoHighLevel Campaigns hold the campaign metadata; individual sends are created as Campaign Messages. We do not migrate send performance data (open rates, click rates) as records; those metrics live in GoHighLevel after cutover once sending resumes.

Acoustic Suppression Lists containing opt-outs, bounces, and Do Not Email markers are exported and imported into GoHighLevel ahead of any Contact import. In GoHighLevel, suppressed addresses are flagged using the HasOptedOutOfEmail field and the original suppression reason stored in a custom field. No Contact may import to GoHighLevel until the suppression load is validated complete.

Acoustic email templates and content blocks export as HTML. Acoustic personalisation tags ($contact.field$ syntax) are documented with their replacement mapping to GoHighLevel Liquid personalisation syntax ({{contact.field}}). The customer reviews each template post-import and updates personalisation tags before the template goes live.

Acoustic Web Tracking events are exported as a Custom Object in GoHighLevel (Event History) with a Contact lookup. Alternatively, high-volume behavioural events are summarised as tags on the Contact record. The approach is chosen during scoping based on event volume and the customer's reporting needs.

Acoustic SMS campaign metadata (audience, schedule, content) migrates as GoHighLevel SMS Campaign records. The underlying Twilio or WhatsApp API credentials do not transfer; the customer provisions a GoHighLevel-integrated messaging account (Twilio, or GoHighLevel's built-in LC Phone system) before SMS sending resumes in GoHighLevel.