Migrate from Leaf360 to Nutshell

Leaf360 People map directly to Nutshell People. All standard properties (name, email, phone, address, job title) migrate as-is. Custom fields on the Person record migrate as Nutshell People custom fields. Primary company link resolves to a Nutshell Company record if one exists; contacts without a company land as standalone People.

Leaf360 Companies map directly to Nutshell Companies. Company name, domain/website, industry, employee count, and annual revenue transfer as standard Nutshell Company fields. Leaf360 parent-company hierarchy migrates using Nutshell's parent-company link field. Multi-company associations collapse to the primary company link with secondary associations noted.

Leaf360 Deals map to Nutshell Deals. Deal name, amount, close date, owner, and custom fields transfer directly. Each Leaf360 pipeline becomes a separate Nutshell pipeline. Leaf360 pipeline stages map value-by-value to Nutshell pipeline stages — this requires pre-migration stage configuration in Nutshell.

Leaf360 Pipelines map 1:1 to Nutshell Pipelines. Each Leaf360 pipeline becomes a new Nutshell pipeline, preserving the pipeline name and associated configuration such as stage count and visible fields. The Nutshell admin must pre‑create matching stages before migration, ensuring that deal records load without validation errors and that stage‑level probability percentages align with the original workflow logic.

Leaf360 pipeline stage names map to Nutshell pipeline stage names value-by-value. We export the full Leaf360 stage list and deliver a stage-mapping specification so the Nutshell admin can create matching stages before migration. Stage probability values apply per Nutshell's configuration model.

Leaf360's referral tracking does not have a direct counterpart in Nutshell, so we retain the referral source as a custom pick‑list field on the People object (e.g., Referral_Source__c). The list of possible values is extracted from Leaf360's configuration and entered as fixed options in Nutshell, guaranteeing that historical referral attribution is preserved across all migrated contacts.

Leaf360 call and email activity logs are migrated as Nutshell Tasks, using the type field to distinguish between calls and emails. Meeting records become Nutshell Events, retaining the original start and end timestamps. All engagement entries keep their original creation date, owner assignment, and links to the related Person or Deal, ensuring a complete activity history in Nutshell.

Leaf360 notes and comments attached to People, Companies, and Deals are migrated as Nutshell Comments, preserving the original author and creation timestamp. Any rich‑text formatting present in Leaf360 is simplified to plain text in Nutshell to maintain compatibility, while the content itself remains fully intact.

Leaf360 custom fields migrate as Nutshell custom fields on the corresponding object. Custom field type mapping: text → text, number → number, date → date, pick-list → pick-list. Pick-list values map value-by-value from Leaf360's defined options. Any Leaf360 custom field without a clear Nutshell type maps to a text field for data preservation.

Files attached to Leaf360 People, Companies, and Deals re-upload to Nutshell as attachments linked to the corresponding record. File name, original upload date, and uploader information are preserved. Large files are subject to Nutshell's attachment size limits.

Leaf360 workflows, sequences, and automations do not migrate. They are source-platform automation constructs with no structural equivalent in Nutshell. We export the Leaf360 workflow definitions as a structured reference document. The team rebuilds automation logic in Nutshell's automation tools using this export as the functional specification.

Leaf360 tags applied to People and Deals are imported as Nutshell Tags, preserving both the tag names and the records they are attached to. Nutshell uses a flat tag namespace, so any hierarchical tag structures from Leaf360 are collapsed into a single level. This approach keeps the tagging system simple while retaining the full set of original labels.

Leaf360 user and owner records resolve against Nutshell users by email address match. Unmatched owners are flagged before migration with a resolution report: either invite the user to Nutshell or assign their records to a fallback owner. No record lands without a valid Nutshell user owner.