Migrate from Apto to Nutshell

Apto contacts migrate to Nutshell people objects. Nutshell people records store name, email, phone, title, and address fields as standard. Apto contact records without a primary company link are attached to a placeholder Nutshell company record to maintain referential integrity. All contact field mappings are validated during the sample migration phase.

Apto companies map directly to Nutshell companies using a one-to-one relationship. Company name, domain/website, industry, employee count, and annual revenue migrate as standard Nutshell fields. Apto parent-company hierarchies map to Nutshell's parent-company field, maintaining organizational structure in the destination system.

Apto deals become Nutshell deals (opportunities). Deal name, amount, stage, and close date migrate directly. Apto property-specific fields including property address, lease dates, square footage, and lease type require Nutshell custom fields since Nutshell has no native real estate property object. Stage names are matched by label during migration.

Apto property records attach to deals as linked objects. The property address, unit/suite, square footage, lease commencement date, and lease expiration date migrate as separate custom fields on the Nutshell deal record. The property name becomes the deal name if the deal name is blank in Apto.

Apto owner IDs are resolved by email match against Nutshell users before migration. Unmatched owners are flagged — your team either creates the Nutshell user first or assigns records to a fallback owner. No record lands without a valid Nutshell owner.

Apto calls and emails migrate as Nutshell tasks with type='Call' or type='Email' respectively. Meetings migrate as Nutshell events preserving original start and end times. Notes migrate as Nutshell activities linked to the parent record. All original timestamps and owner assignments are preserved during the activity migration phase.

Apto custom fields on contacts migrate to Nutshell custom fields on people. Field type mapping applies: Apto text fields become Nutshell text fields, pick-list fields become Nutshell choice fields. Required-field settings in Apto do not transfer — re-apply in Nutshell after migration.

Apto custom fields on deals migrate to Nutshell deal custom fields. Nutshell requires Pro or Enterprise plan tier for deal-level custom fields — we confirm your plan level before migration. Custom field creation is included within the migration scope at no additional charge for eligible plans.

Apto file attachments on contacts, companies, and deals are downloaded from Apto's storage and re-uploaded to the corresponding Nutshell record. File size limits apply — Nutshell's API supports files up to 25MB per attachment. Inline images embedded in notes are extracted and re-hosted as separate attachments.

Apto leads with status 'New', 'Contacted', or 'Qualified' migrate to Nutshell leads. Lead status values are mapped value-by-value between systems. Unqualified Apto leads with no associated deal history route directly to Nutshell leads for future follow-up and conversion tracking.

Apto activity records including calls, emails, meetings, and notes carry their original create timestamps into Nutshell's activity feed on each record. Activity owner transfers are completed via email matching logic. Deleted or archived activities in Apto are excluded from the migration to maintain data accuracy.

Apto workflows, sequences, and deal-stage automation rules do not have a direct Nutshell equivalent. FlitStack AI exports Apto workflow definitions as a structured JSON file containing stage triggers, assigned tasks, and notification rules. Your team can use this export as a reference when rebuilding automations in Nutshell's automation builder.