Migrate from Actito to Nutshell

Discovery and source audit

We audit the Actito portal across licence tier, Profile schema, all Custom Table definitions and their relationship links, Entity assignments and their scope, active scenario count and complexity, campaign configurations and targeting criteria, engagement interaction volume, and push notification device token volume. We identify which Actito API version each export job uses to catch any V4 deprecation overlaps. The discovery output is a written migration scope and field mapping specification that the customer reviews and approves before migration begins.

Destination schema provisioning in Nutshell

We pre-create all custom fields in Nutshell (on Person and Company objects) before any data import. This includes Actito custom table fields mapped to custom fields, subscription and consent fields, GDPR attribute fields, push token fields, and any Actito attribute that has no native Nutshell equivalent. Field types are validated against Nutshell's supported types (Text, Long Text, Number, Currency, Date, Checkbox). We configure Teams or custom partition fields if the customer uses Actito entities for data separation.

Company deduplication and Person-Company linkage planning

We extract all company affiliation data from Actito Profiles, apply domain-based matching and fuzzy name matching to identify duplicate companies, and collapse them into a unique company list before import. Each unique company becomes a Nutshell Company record. We then map each Actito Profile to a Person record with the resolved CompanyId lookup so the Person-to-Company relationship is satisfied at import time rather than repaired post-import.

Export with rate-limit management and bulk compression

We extract Profile records, Custom Table records, engagement data, and push device tokens from Actito using ETL export jobs with GZIP compression rather than looping API calls to respect the 100 calls-per-minute rate limit. Large profile sets are split into multiple export batches. We validate export completeness (row counts, linked record counts) against the discovery inventory before proceeding to transform.

Transform, custom table flattening, and field mapping execution

We run the field mapping specification against the extracted data. Custom table fields flatten into Person or Company custom fields per the schema mapping. Relationship fields between custom tables resolve to single-value fields. Subscription preferences and GDPR consent data populate the actito_ consent custom fields on Person. Engagement records convert to Nutshell Activity records. Push device tokens and opt-in status populate custom fields on Person. The transform output is a set of CSV files ready for Nutshell import.

Staging import and reconciliation

We run a full import into a Nutshell staging environment using production-like data volume. The customer's admin reconciles Person counts (imported vs expected), Company counts, custom field populated rate, and Activity count. We resolve any Company lookup failures, required-field violations, or dedupe conflicts before production import. Sign-off on the staging results authorizes the production migration window.

Production migration, cutover, and scenario handoff

We freeze Actito writes during cutover, run a final delta export of any records modified during the migration window, and execute the production import in dependency order: Companies first, then Persons with CompanyId resolved, then Activities. We deliver the scenario and campaign inventory document to the customer's admin team for Nutshell workflow rebuild evaluation. We do not rebuild Actito scenarios in Nutshell inside the migration scope. Post-migration, we provide a reconciliation report and a one-week hypercare window for data quality issues.