Migrate from Acoustic Campaign to Zoho CRM

Acoustic Contacts within each Database may have different schemas (custom field sets) per Database. We route each Database to a separate Zoho CRM module or Custom Module. Contacts with a Lifecycle Stage of 'customer' or 'sales qualified' route to Zoho Contact; all others route to Zoho Lead. The original Database name and schema identifier preserve in custom fields for audit. If a single email appears across multiple Databases, we deduplicate by selecting the record with the most recent ModifiedDate as the canonical version and flag duplicates in a migration_duplicates__c custom field.

Each Acoustic Database is a separate schema container with its own field definitions. We map each Database to either a Zoho CRM standard module (Leads, Contacts, Accounts) or a Custom Module (Database_Name__c) depending on whether the Database contains account-level or contact-level records. The Zoho module is provisioned with all custom fields before any data imports into that module begin.

Acoustic Relational Tables hold transactional or behavioural data joined to Contacts via a key field. We export the Relational Table rows and recreate them as a Zoho CRM Custom Module (TableName__c). A Lookup field on the Zoho Contact or Lead (lookup_to_contact__c) links each row to the parent Contact using the Acoustic relational key. We document the original join logic and the Lookup field name for the customer's admin to reference when building Zoho CRM reports.

Acoustic Queries are saved filter definitions evaluated at send time. The Query export gives a snapshot of current Contact membership. We export each Query's member list as a CSV and import it into Zoho CRM as a Tag (tagging each Contact in the membership) plus a Custom View named after the Query for ongoing filtering. The original Query filter logic is documented in the automation inventory handoff document.

Acoustic Suppression Lists hold opted-out, bounced, and Do Not Email addresses. We export all suppression entries and map them to Zoho CRM Contact records by email match, setting the HasOptedOutOfEmail flag to true for each suppressed address. If the suppressed address has no matching Contact record, we create a minimal Contact record with just the email and HasOptedOutOfEmail=true to preserve the suppression. Suppression Lists migrate before any Contact import to prevent re-mailing.

Acoustic Programs are multi-step automated message sequences with branching, timers, and conditional logic. Programs are not migratable as code to Zoho CRM because the trigger models and action sets differ structurally. We export the Program definition (steps, branches, timer durations, audience criteria) and deliver a written inventory with a recommended Zoho Workflow Rule or Blueprint equivalent for the customer's admin to rebuild post-migration.

Acoustic Mailings (autoresponders, recurring sends, one-off campaigns) migrate as Zoho CRM Campaign records with Campaign Name, Subject, Status, Start Date, and End Date. The HTML content migrates to the Campaign's HTML Description or is stored as an attachment. Active scheduling is not carried across; the customer's admin reschedules sends in Zoho CRM.

Acoustic email templates export as HTML with Acoustic-specific personalisation tokens ($contact.field$). We translate tokens to Zoho CRM Liquid markup (${contact.field}) and store the converted HTML in Zoho CRM Email Templates. Any $contact.program_id$ or $contact.program_name$ tokens that referenced Acoustic Program context are flagged in the template inventory for manual review.

Acoustic Web Tracking captures page visits and on-site behaviour tied to Contacts. We export behavioural event history and import it as Zoho CRM Tasks (type=Note) with the Subject as the event description and Description containing the page URL and timestamp. The Task links to the Contact via WhoId. High-volume behavioural data (thousands of events per Contact) may be summarised into a single Note record per event category to avoid record volume inflation.

Acoustic Users referenced on Contacts, Relational Table rows, and Program enrollments map to Zoho CRM Users by email address. We extract all distinct Acoustic User emails, match against the Zoho CRM User table, and flag any User without a Zoho match for the customer's admin to provision before record migration resumes.

Acoustic Databases contain custom Contact fields defined per Database. We map each custom field to a Zoho CRM Custom Field of the matching type (Text, Number, Date, Picklist, Boolean, etc.) on the appropriate module (Contact or Lead). Picklist custom fields require the destination picklist values to be created in Zoho CRM before import.

Acoustic engagement records for emails sent, opened, and clicked migrate as Zoho CRM Tasks. Each engagement type (send, open, click) becomes a separate Task record with the Task Subject describing the action (e.g., 'Email Sent: Spring Newsletter'), the Description containing the email subject line and timestamp, and the Activity Date matching the original Acoustic engagement timestamp. The Task links to the Contact via WhoId.