Migrate from Ortto to Nutshell

Discovery and scoping

We audit the Ortto account across plan tier, People count, Account count, tag taxonomy, custom field definitions (including field types and picklist options), Audience count and filter logic, Activity volume and event types, and active Journeys and Playbooks. We confirm the Ortto instance region (AU, EU, or default) to configure the correct API endpoint. We extract the full People and Account schemas including all custom field definitions and aggregate field flags. We document active Journeys and Playbooks as written flow specifications. The discovery output is a written migration scope with object counts, field mapping table, and a pricing model comparison (Ortto flat-rate vs Nutshell per-user).

Tag taxonomy export and Nutshell field provisioning

We export the complete Ortto tag taxonomy (all tag names) and tag assignments per Person record. We create a custom multi-select picklist field in Nutshell (tag_names__c) and populate the picklist options with the exported tag names. If the tag taxonomy exceeds Nutshell's picklist option limits, we configure a text field with pipe-delimited tag values instead. Custom fields from Ortto are pre-created in Nutshell before any record migration begins. Aggregate field types are flagged for manual post-migration recreation.

Account and Company migration

We extract all Ortto Account records (name, domain, industry, employee count, annual revenue, location) and import them into Nutshell as Company records. Custom Account fields map to Nutshell Company custom fields. The Account-to-Company migration runs first because Nutshell Contacts require a Company reference for linking. We run deduplication checks using domain as the match key and flag any duplicate Account names for the customer to resolve before proceeding.

People and Contact migration with tag assignment

We extract all Ortto People records with standard fields and custom field values, then import into Nutshell as Contacts. The Ortto email address is the dedupe key. Each Contact's associated Account is resolved using the Company mapping from Step 3. Tag assignments from the tag taxonomy export populate the Nutshell tag_names__c multi-select field. Lifecycle stage from Ortto migrates as a text custom field on Nutshell Contact. After import, we run a row-count reconciliation against the Ortto People export to confirm all records transferred.

Activity migration and Audience-to-Group conversion

We extract Ortto Activity records (event type, timestamp, associated Person) and import them as Nutshell Activity records of type 'Note' linked to the migrated Contact. The original event type is preserved in a custom field (activity_type__c). We then convert each Ortto Audience to a static Nutshell Contact Group: we apply the audience filter conditions against the migrated Contact data, identify matching records, and create a Nutshell Contact Group containing those contacts. Dynamic re-segmentation based on live behavior is documented as a limitation and communicated to the customer.

Cutover, validation, and automation inventory delivery

We freeze Ortto writes during cutover and run a final delta migration of any records modified during the migration window. We validate record counts across all objects, spot-check 25-50 records against the source data, and deliver the Journey and Playbook inventory document to the customer's admin team for manual rebuilding. We do not rebuild Journeys or Playbooks as Nutshell automation rules inside the migration scope; that work requires a separate scope or an internal admin task. We support a one-week hypercare window to resolve reconciliation issues raised by the customer's team.