CRM migration
Field-level mapping, validation, and rollback between Acoustic Campaign and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Acoustic Campaign
Source
Nutshell
Destination
Compatibility
5 of 8
objects map 1:1 between Acoustic Campaign and Nutshell.
Complexity
BStandard
Timeline
2-4 weeks
Overview
Moving from Acoustic Campaign to Nutshell is primarily a contact and company migration rather than a full marketing automation carryover. Acoustic Campaign organizes contacts inside Databases with Relational Tables for transactional data and Programs for automation flows; Nutshell uses a flat People and Organizations model with a built-in CRM. We extract each Acoustic Database independently, apply deduplication logic where the same email appears across multiple Databases, load People and Organizations into Nutshell via its REST API, and preserve opt-in and opt-out status as Nutshell's unsubscribe flags. Acoustic Programs and Queries do not migrate as code; we deliver a written inventory of each Program's structure and each Query's current membership for the customer's admin to rebuild in Nutshell's workflow builder. Suppression Lists migrate ahead of any contact import to prevent sending to previously opted-out addresses on day one.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Acoustic Campaign object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Acoustic Campaign
Contact (per Database)
Nutshell
People
1:1Each Acoustic Campaign Database exports as a distinct People batch. We load each batch into Nutshell People, using email as the dedupe key. Where the same email appears across multiple Databases, we apply a customer-approved merge strategy (typically the most recently updated record wins, with suppressed status and custom field values merged). The original Acoustic Database name is preserved in a custom People field acoustic_database__c for audit.
Acoustic Campaign
Database schema (custom fields)
Nutshell
People custom fields
lossyAcoustic per-Database custom Contact fields export with each Database. We pre-create matching custom fields in Nutshell's People custom field settings before import, mapping field types (text to text, date to date, picklist to dropdown) and preserving field labels in a field_mapping document for the customer's admin to review.
Acoustic Campaign
Organization
Nutshell
Organizations
1:1Acoustic Relational Tables that represent company-level data (e.g., a Relational Table keyed on company_id with account_manager, contract_value, or tier fields) denormalize onto the corresponding People record as People custom fields in Nutshell, since Nutshell Organizations do not support free-form custom fields without a paid integration. We document the denormalization so the customer's admin can populate the matching Organization record manually post-import.
Acoustic Campaign
Query (snapshot membership)
Nutshell
People tags and lists
1:1Acoustic Queries produce a current snapshot of Contact membership at export time. We export each Query as a static People list and import it into Nutshell as a People tag or a static People list. The Query logic itself (the server-side join rule) cannot migrate; we document each Query's definition and the customer rebuilds equivalent filters using Nutshell's CRM filter builder.
Acoustic Campaign
Suppression List
Nutshell
People unsubscribe records
1:1Acoustic Suppression Lists (opt-outs, bounces, Do Not Email markers) export as email addresses and status codes. We load these into Nutshell ahead of any People import by setting the unsubscribe flag on each matching People record or creating a People record with unsubscribe status for addresses that do not yet exist. This prevents any welcome or campaign send to a previously opted-out address on day one.
Acoustic Campaign
Program (structure)
Nutshell
Workflow inventory document
lossyAcoustic Programs with branching, timers, and enrollment triggers export as a written inventory: program name, trigger type, step sequence, conditions, and message content. We do not migrate Program logic as executable code. The customer uses the inventory document to rebuild equivalent workflows in Nutshell's Workflow builder, with timers and conditions re-implemented using Nutshell's step logic.
Acoustic Campaign
Mailing (content)
Nutshell
Email template inventory
lossyAcoustic Mailing HTML content exports as a written asset inventory with subject, sender, send date, and HTML body. Acoustic personalisation tags ($contact.field$) are documented with their replacement syntax so the customer's admin can translate them to Nutshell's {{contact.field}} template syntax when rebuilding email templates in Nutshell's email builder.
Acoustic Campaign
Owner
Nutshell
Nutshell user
1:1Acoustic contact Owner records resolve by email against Nutshell user accounts. Any Acoustic Owner without a matching Nutshell user is held in a reconciliation queue for the customer's admin to provision before the People import resumes.
| Acoustic Campaign | Nutshell | Compatibility | |
|---|---|---|---|
| Contact (per Database) | People1:1 | Fully supported | |
| Database schema (custom fields) | People custom fieldslossy | Fully supported | |
| Organization | Organizations1:1 | Fully supported | |
| Query (snapshot membership) | People tags and lists1:1 | Fully supported | |
| Suppression List | People unsubscribe records1:1 | Fully supported | |
| Program (structure) | Workflow inventory documentlossy | Fully supported | |
| Mailing (content) | Email template inventorylossy | Fully supported | |
| Owner | Nutshell user1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Acoustic Campaign gotchas
OAuth API ceiling of 10 concurrent requests limits migration throughput
Multiple Databases do not collapse cleanly into a single destination list
Relational Table joins are evaluated server-side, not exportable as joined data
Programs export structure but not real-time enrollment state cleanly
Suppression Lists must migrate before Contacts to honour opt-outs
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
Discovery and scope definition
We audit the source Acoustic Campaign account across Database count, total contact volume per Database, custom field definitions per Database, Relational Table structures referenced by Queries, active Suppression Lists, and active Programs. We confirm the deduplication strategy with the customer's team (which record wins when an email appears in multiple Databases), identify any Relational Table fields to denormalise onto People records, and flag any Program or Query structures that require rebuild in Nutshell. The discovery output is a written scope document and a migration sequence plan.
Nutshell custom field and user provisioning
We create custom People fields in Nutshell matching every custom Contact field exported from each Acoustic Database. We verify Nutshell user accounts for each Acoustic Owner referenced in the data, flagging any missing users for the customer's admin to provision before the People import begins. If Relational Table data is being denormalised, we confirm which fields attach to People versus which the customer will maintain manually in Nutshell Organizations.
Suppression List export and load
We export all Acoustic Suppression List entries (opt-outs, hard bounces, unsubscribes, Do Not Email markers) as a deduplicated email list with status codes. We load these into Nutshell ahead of any People import, setting the unsubscribe flag on matching People records and creating suppressed People entries for addresses that do not yet exist. We validate the suppression count in Nutshell and run a no-send test against a sample of 10-20 suppressed addresses to confirm the flag is active.
People export, deduplication, and load
We export Contacts from each Acoustic Database independently, preserving all standard fields (name, email, phone, address, opt-in date, created date) and custom fields. We apply the customer-approved deduplication strategy across all Databases, producing a unified People load file. The unified file loads into Nutshell via the Nutshell API, with assigned_to_user_id resolved via the Owner-to-User mapping table. Each phase emits a row-count reconciliation report confirming the number loaded matches the source minus suppressed entries.
Query snapshot and Program inventory delivery
We export the current membership snapshot of each Acoustic Query as a static People list and import it into Nutshell as People tags or lists. We deliver the Query definitions in a written inventory document that the customer's admin uses to rebuild equivalent CRM filters in Nutshell. We deliver the Program structure inventory (step sequence, trigger type, conditions, message content) in a written document for the admin to rebuild in Nutshell's Workflow builder. Neither Queries nor Programs migrate as executable logic.
Cutover, validation, and handoff
We freeze writes in Acoustic Campaign during the cutover window, run a final delta export of any records modified since the initial export, and load the delta into Nutshell. We confirm the total People count in Nutshell matches the reconciled source count. We deliver the Query and Program inventory documents to the customer's admin team. We support a 48-hour post-cutover window for reconciliation issues raised by the sales team. We do not rebuild Acoustic Programs as Nutshell Workflows inside the migration scope; that work uses the delivered inventory as its source document.
Platform deep dives
Acoustic Campaign
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Acoustic Campaign and Nutshell.
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Acoustic Campaign: Up to 10 concurrent requests per account when authenticated via OAuth; throttle responses returned beyond the ceiling.
Data volume sensitivity
Acoustic Campaign exposes a bulk API — large-volume migrations stream efficiently.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Acoustic Campaign to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Acoustic Campaign to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Acoustic Campaign
Other ways to arrive at Nutshell
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.
