Migrate from Acoustic Campaign to monday CRM

Acoustic Campaign Contacts migrate as Items within the destination Monday.com CRM board representing the source Database. Each Contact's email, name, phone, and custom field values become column values on the Item. Email serves as the dedupe key during import. Contact status (active, suppressed, bounced) maps to a monday.com CRM status column value. Contacts with the same email appearing across multiple Acoustic Databases route to the corresponding board based on the source Database identifier.

Each Acoustic Campaign Database maps to its own Monday.com CRM board. The Database name becomes the board name, and the Database's field schema (system fields plus custom fields) is reconstructed as columns in the destination board. Accounts commonly have multiple Databases with overlapping schemas; we split them into separate boards rather than attempting to collapse them into one board, preserving the original data isolation that the Database architecture enforced.

Relational Tables in Acoustic hold transactional or behavioural data joined to Contacts via a key. Since Monday.com CRM Items do not support relational joins, we denormalise the most-referenced Relational Table columns onto each Contact Item as custom columns. High-cardinality or rarely-referenced fields may alternatively be stored as a separate board linked by the contact email as a text column for lookup. The customer chooses the denormalisation strategy during scoping based on how the Relational Table data is used in daily operations.

Acoustic Queries are saved filter definitions over Contacts plus Relational Table joins. The current membership snapshot of each Query migrates as a Group within the corresponding board, with all Items in the Group representing the contacts that were members at export time. The server-side join logic does not migrate; we deliver a written description of each Query's conditions so the customer's admin can recreate equivalent filtering groups in Monday.com CRM.

Suppression List entries (opted-out addresses, hard bounces, Do Not Email markers) migrate first, before any Contact import, to Tags on the board or to a dedicated suppression-tracking board. We tag each suppressed email address with a suppression reason tag. During contact import, any address matching a suppression tag is flagged and excluded from active sending lists. This sequencing honours CAN-SPAM and GDPR obligations and prevents the first post-migration send from reaching addresses that previously opted out.

Acoustic Programs are multi-step automated message sequences with branching, timers, and enrollment state. Programs do not migrate as automation code because the underlying trigger-action model differs fundamentally from Monday.com's recipe-based automations. We deliver a written Program inventory that documents each Program's trigger, steps, conditions, timer delays, and branching logic, with a recommended Monday.com automation equivalent. The customer's admin rebuilds the automations post-migration using Monday.com's Automations or AI Recipes features.

Acoustic Mailing metadata (name, subject, sender address, schedule, audience size, send status) migrates as a Monday.com CRM Campaign entry if the customer uses Monday Campaigns. HTML email body migrates as content, though Acoustic-specific personalisation tags ($contact.field$ syntax) do not resolve in Monday.com CRM and require translation to Monday's templating format. The underlying mailing infrastructure (Acoustic's send infrastructure, bounce handling, delivery optimisation) does not carry across; Monday Campaigns uses its own send engine.

Acoustic Web Tracking events capture on-site behaviour tied back to Contacts. We export event history as a JSON or CSV log and attach it to each Contact Item as a separate column (text or long text) containing a serialised activity log of page visits, form submissions, or purchase events. Full behavioural event continuity requires rebuilding tracking in Monday.com CRM via the website embed or an integration partner; we document the event schema for the customer's implementation team.

Acoustic email templates and reusable content blocks export as HTML. Acoustic-specific personalisation tags ($contact.field$) do not carry across; we document each template's tag usage and deliver a tag-translation reference for the customer's admin to rebuild in Monday.com's template editor. HTML without personalisation tags can be imported directly as content blocks within Monday Campaigns.