Migrate from matrix to Nutshell

Matrix contacts map directly to Nutshell People. The primary company association migrates to the Nutshell Company lookup. If a Matrix contact has no associated company, it lands as a standalone People record. Original create dates are preserved in a custom field since Nutshell's createdAt timestamp reflects the migration import time.

Matrix contacts marked as prospects without a closed-won deal route to Nutshell Lead records. Teams that use Matrix's lifecycle status field to distinguish raw leads from active opportunities benefit from this split — Nutshell Leads have their own pipeline view and qualification workflow distinct from People records.

Matrix companies map 1:1 to Nutshell Companies. Company hierarchies (parent/child relationships in Matrix) are preserved using Nutshell's parent company field, with child records migrated after their parents to maintain referential integrity. Industry classification maps value-by-value where Matrix's industry taxonomy overlaps with Nutshell's pick-list; non-matching values land as free-text custom fields to preserve the original data without loss.

Matrix deals migrate as Nutshell Deals with the deal name, amount, expected close date, and owner preserved. Pipeline membership determines which Nutshell pipeline the Deal joins — if Matrix has multiple pipelines, Nutshell's Pro plan or above is required since it supports up to 5 pipelines.

Each Matrix pipeline becomes a separate Nutshell pipeline. Pipeline stages in Matrix map to Nutshell stage values on a per-pipeline basis. Stage order and probability percentages are preserved exactly as configured in Matrix. Nutshell's stage-entry timestamps surface in the Deal record's stage history for reporting continuity and historical tracking.

Matrix engagement records of type call, email, and meeting map to Nutshell Activities linked to the parent People, Company, or Deal record. Original timestamps and activity owners are preserved. The activity type field maps to Nutshell's activity type pick-list (Call, Email, Meeting, Task).

Matrix notes migrate as Nutshell Activity records with type 'Note.' Rich-text formatting is preserved through the conversion process. Notes linked to specific records carry the parent reference in Nutshell for direct navigation. Standalone notes without a parent are imported as unlinked activities for manual reassociation by your team post-migration.

Matrix custom properties on contacts become Nutshell custom fields on the People object. Your Nutshell admin creates the custom field in Settings > Custom Fields before the migration runs. We flag any custom property that requires a field type not available in your Nutshell plan — for example, Nutshell Foundation limits custom fields to 5 total.

Matrix company-level custom properties migrate to Nutshell Company custom fields. These must be pre-created in Nutshell's Company tab under Settings > Custom Fields. If your Nutshell plan limits custom fields, we prioritize the highest-value properties and surface the remainder for post-migration re-entry.

Matrix deal-level custom properties map to Nutshell Deal custom fields. These require pre-creation in Nutshell's Deal settings before data lands. Value-mapping for pick-list properties is applied at migration time when pick-list values differ between platforms, ensuring consistent dropdown selections in the destination system.

Matrix file attachments are downloaded and re-uploaded to Nutshell's file storage. File size limits apply — Nutshell supports standard file uploads on records with reasonable size caps per the platform's documentation. Inline images embedded in notes are extracted and rehosted separately.

Matrix owner assignments resolve to Nutshell users by email match. Unmatched owners are flagged before migration — your team either creates Nutshell user accounts for them first or assigns records to a fallback owner. Records never land in Nutshell without a valid user assignment.