Migrate from Dialytica - Marketing Automation Platform to Nutshell

Discovery and export feasibility assessment

We audit the Dialytica account for available export mechanisms: admin CSV exports, database dumps if accessible, or manual extraction from the UI. We catalog every object in scope (Contacts, Call Campaigns, SMS Campaigns, Call Records, QA Reviews, SMS Activities, Users, Templates), estimate record counts per object, and assess data quality. If no automated export is available, we design a manual extraction process and adjust the timeline and cost accordingly. We also identify the Nutshell target schema (People, Companies, Deals, Campaigns, Activities, custom fields) at this stage.

Schema design and custom field configuration plan

We design the destination Nutshell schema. This includes creating custom fields on People for QA scorecard dimensions, configuring Deal stages aligned with the customer's sales process, setting up Campaigns for each Dialytica call and SMS campaign, and designing the Activity-to-Person relationship so that call and SMS history appears on the correct contact timeline. We deliver a schema diagram and a custom field configuration checklist for the customer's Nutshell admin to implement before data import begins.

Data extraction and staging

We extract data from Dialytica using whatever mechanism is available (CSV export, manual dump, or API if accessible). We stage the raw data in a migration workspace and run a pre-mapping audit: deduplication by email address, identification of malformed records, and detection of records with missing required fields for Nutshell. We also identify any cross-channel contacts that appear in both call and SMS campaigns so that their activity history merges correctly into a single Nutshell People record.

Sandbox staging migration and reconciliation

We run a full migration into a Nutshell sandbox environment using production-like data volume. The customer's admin reviews record counts (People imported, Companies created, Activities logged, Deals opened), spot-checks twenty to thirty random records against the Dialytica source, and validates that call dispositions, SMS delivery statuses, and QA scores appear correctly in Nutshell. Any mapping corrections are documented and applied before the production migration phase begins.

Production migration in dependency order

We run the production migration in record-dependency order: Nutshell configuration (custom fields, pipelines, campaign setup) validated first, then Companies created from Dialytica contact-level company data, then People imported with company lookup resolved, then Campaigns created for each Dialytica call and SMS campaign, then Activities (calls and SMS logs) attached to the resolved People records, then QA Review data mapped to custom fields and Activity notes. Each phase emits a row-count reconciliation report before the next phase begins.

Cutover, validation, and automation rebuild handoff

We freeze writes in Dialytica during cutover, run a final delta migration of any records modified during the migration window, then enable Nutshell as the system of record. We deliver a written inventory of every Dialytica campaign (call and SMS), call script, SMS template, and AI targeting rule requiring rebuild in Nutshell. The customer's admin uses this document to configure Nutshell Campaigns, email templates, and list segmentation. We do not rebuild automations or sequences as part of the standard migration scope.