Migrate from Insightly Marketing to Nutshell

Insightly Contact records map directly to Nutshell Person records (Contacts in API terminology, People in the UI). We preserve first name, last name, email, phone, address, and any custom field values. Lifecycle stage and owner assignment from Insightly map to Nutshell custom Person fields since Nutshell does not have a native Lifecycle Stage property. Tags on Insightly Contacts migrate as comma-separated values in a Nutshell custom multi-select field.

Insightly Organization records map to Nutshell Account records (Companies in the UI, Accounts in the API). Organization name, domain, address, industry, and custom fields migrate. Organization-to-Contact links are preserved as Person-to-Account association records in Nutshell. Organization-to-Organization relationships (parent-subsidiary) map to Account-to-Account association records.

Insightly's separate Lead object requires a migration decision: if the destination Nutshell account uses the Lead feature for unqualified prospects, Insightly Leads map to Nutshell Leads with status preserved in a custom field. If the team uses only People in Nutshell, Insightly Leads merge into Person records with Lead status stored in a custom field. The customer chooses during scoping. We flag which approach preserves more reporting continuity.

Insightly Opportunities map to either Nutshell Leads or Deals depending on the destination configuration. Pipeline names and stage values map to Nutshell pipeline stages. Probability percentages, expected close dates, and amount fields migrate as custom fields or native fields depending on the Nutshell tier. Closed-Lost and Closed-Won reasons from Insightly custom properties become Nutshell Deal loss reason fields.

Nutshell has no native Project object. Insightly Projects migrate as a structured set of linked Activities on the associated Account (or Person). We extract project name, status, milestones, and milestone dates, and recreate them as Nutshell Tasks and Events with a project reference stored in a custom field. The project-to-contact and project-to-organization links become Activity associations. Customers who need full project management capability should plan for a separate project tool alongside Nutshell.

Insightly Task records migrate to Nutshell Task records with due date, assignee (resolved via User mapping), status, priority, and related-to reference (Contact, Organization, Opportunity, or Project) preserved. Task content migrates as the Nutshell Task description. If the related Project is present, the Task links to the Account that carries the project history.

Insightly custom fields and custom field groups vary per customer instance and require a schema discovery phase before migration. We map each custom field's name, type (text, number, date, picklist, checkbox, currency), and values. Custom field groups in Insightly organize related fields; these groupings are documented but do not map to a specific Nutshell construct since Nutshell uses flat custom field lists on each object.

Insightly Custom Objects extend standard objects (Contacts, Organizations, Opportunities) with user-defined schemas. Since Nutshell does not have standalone custom object types, we flatten Insightly Custom Object records into custom fields on the parent standard object (Account or Person). Lookup relationships between custom objects become custom lookup fields or denormalized ID fields depending on the relationship cardinality.

Insightly User records map to Nutshell User accounts by email match. We resolve every distinct Owner referenced on Contact, Organization, Opportunity, and Project records against the destination Nutshell Users. Owners without a matching Nutshell User go to a reconciliation queue for the customer's admin to provision. Owner assignment on records migrates once User mapping is complete.