Migrate from Acoustic Campaign to Freshsales

Acoustic Contacts migrate to Freshsales Contacts with the primary Database's schema as the target. Each Contact's email address serves as the dedupe key. We load Suppression Lists before Contacts to prevent opted-out addresses from receiving any Freshsales-initiated sends during or after migration.

Each Acoustic Database maps to its own Freshsales Contact List (for the customer's Freshmarketer instance) or to an Account-based segmentation filter. If the customer uses Freshsales CRM without Freshmarketer, we collapse multiple Databases into one contact pool and flag duplicates where the same email appears across Databases, keeping the record with the most recent modification date.

Relational Table rows do not have a native Freshsales equivalent. We denormalise the most-used Relational Table fields onto the parent Contact or Account as custom fields. The full Relational Table row set migrates as a JSON-encoded custom field value or as a separate lookup table the customer can reference. The join logic (Query definitions) is documented for the admin to rebuild as Freshsales filter views.

Acoustic Queries define saved segment membership using Relational Table joins evaluated at send time. We export the current Contact membership snapshot for each Query and import it as a Freshsales Contact List. The Query filter logic is documented in the rebuild inventory; Freshsales filters replicate the audience selection but the Relational Table join logic must be rebuilt as denormalised field conditions.

Acoustic Suppression Lists (opt-outs, bounces, Do Not Email markers) migrate to Freshsales Do Not Contact (DNC) list. We load this first, before any Contact import, and validate that the DNC count in Freshsales matches the Acoustic suppression total before enabling any Freshsales sending capability. This sequencing prevents the CAN-SPAM and GDPR exposure of mailing an address that previously opted out.

Acoustic Programs are multi-step automated message sequences with branching and timer-based enrollment state. They do not migrate as automation code to Freshsales. We export the Program definition (steps, branches, timers, audience criteria) and deliver a written rebuild inventory with a recommended Freshsales Workflow equivalent for each Program. The customer's admin rebuilds the Workflows post-migration; we do not configure Freshsales Workflows as standard scope.

Acoustic Mailing metadata (name, subject, sender, schedule, HTML content) migrates as Freshsales Email Templates. Acoustic personalisation tags ($contact.field$) are translated to Freshsales Liquid-style personalisation syntax. Active autoresponder schedules are documented; the trigger logic requires a Freshsales Workflow to recreate the send condition.

If Acoustic CRMi has been syncing Company data from an upstream CRM, those Company records migrate to Freshsales Account. The mapping uses domain or Company name as the dedupe key. Account-Contact relationships resolve at migration time so that each Contact has a parent AccountId before the Contact import phase begins.