Migrate from Acoustic Campaign to Twenty CRM

Acoustic Campaign Contacts migrate to Twenty CRM People records. The contact's email address serves as the dedupe key. For contacts that represent organisations rather than individuals (common in B2B Acoustic databases), we map to Twenty Company records instead, or to Person records linked to an appropriate Company record if a match exists in the destination. The Acoustic contact identifier is preserved in a custom twenty_original_id__c field for audit traceability.

Each Acoustic Database is treated as a separate source schema. When the same contact email appears in multiple Acoustic Databases, we run a deduplication pass using the most recent ModifiedDate across all Databases as the source of truth. The winning record's full field set is imported; others are flagged in a deduplication report. If Databases represent distinct business units, we optionally create a Company record per Database as a grouping tag in Twenty rather than collapsing to a single pool.

Acoustic Relational Tables hold transactional or behavioural data joined to Contacts via a shared key. We export each Relational Table's rows independently and recreate them as Twenty Custom Objects with the same column names and types. We add a lookup field (personId or companyId) to the Custom Object schema and populate it by resolving the join key from the source table against the migrated Person records. The Query membership snapshot for each Relational Table is exported as a CSV of contact email addresses and migrated as a tag set or custom field on the relevant Person records.

Acoustic Queries define saved filter logic over Contacts and Relational Tables that is evaluated at send time. The Query export gives current membership as a snapshot list of email addresses. We import each Query's membership snapshot as a tag set (multi-select or comma-separated custom field) on the relevant Person records in Twenty. The filter logic itself does not carry across; we document each Query's definition in the handoff inventory so the customer's admin can rebuild it as a saved filter view in Twenty if needed.

Acoustic Suppression Lists hold opted-out, bounced, and Do Not Email addresses. We load suppression entries into a Twenty custom object (e.g. optOutEntry) with email, suppressionReason, and suppressionDate fields before any Person import begins. This prevents any migrated suppression address from receiving a welcome or test send during the cutover window. After migration, the customer's admin configures a pre-send check in Twenty or their sending tool that queries this custom object before dispatching.

Acoustic Programs are multi-step automated sequences with enrollment state, branching, and timer logic. Twenty CRM does not include a native workflow or journey builder in its core product. We export the full Program definitions including steps, conditions, timer configurations, and enrollment counts, and deliver them as a written inventory with step-by-step descriptions and the recommended rebuild approach in an external automation tool (n8n, Make, or a custom API-based workflow). We do not migrate Programs as executable code.

Acoustic Mailings (campaign sends, autoresponders, recurring campaigns) export with name, subject line, sender address, schedule, and HTML content. We deliver the HTML content and metadata as a structured content inventory. The sending infrastructure (Acoustic's email, SMS, push, WhatsApp channels) does not carry to Twenty; the customer's admin selects which mailing content to repurpose in their new sending platform.

Acoustic Web Tracking events capture page visits and on-site behaviour tied back to Contacts. We export the event history as a CSV of personEmail, eventType, eventTimestamp, and eventPayload, and import these as Twenty Activities linked to the corresponding Person records. The event schema is recreated as a custom Activity type in Twenty so the activity timeline shows behavioural history alongside calls, emails, and meetings.

Acoustic email templates and reusable content blocks export as HTML. Acoustic's $contact.field$ personalisation syntax is translated to the destination's tag format (Liquid, Handlebars, or plain placeholder notation) as part of the content inventory. The templates themselves do not import as live assets into Twenty because Twenty does not include an email template editor; they are handed off as HTML files for use in the customer's chosen sending platform.

Acoustic Campaign Stores owner assignments on Contacts and Program enrollments. We extract distinct owner identifiers and attempt to match by email against the Twenty workspace's User table. Any owner without a matching Twenty User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignments on migrated records are updated once User resolution is confirmed.