Migrate from Capsule CRM to Nutshell

Capsule stores individual Contacts and Organisations as a unified Party object with a type indicator. We split each Capsule Party at migration time using the type field, creating separate People and Organisation records in Nutshell. Email address, phone, address, owner assignment, and all standard fields carry forward. Capsule tags on Parties attach to the corresponding Nutshell People or Organisation record. Custom fields on Parties use Capsule's data-tag system and require definitions fetched separately from the /fields/definitions endpoint for parties, opportunities, and cases before values can be correctly typed and mapped to Nutshell's custom fields. List-type custom fields require option set resolution, and note-type fields may lose formatting including line breaks and bullet points on export.

Capsule Opportunities map 1:1 to Nutshell Opportunities with pipeline name, stage name, probability, expected close date, value, currency, owner, and linked Party preserved. Nutshell's lower-tier plans restrict the account to one pipeline and lock advanced reporting behind higher plans; if the source Capsule account uses multiple pipelines, we flag this at scoping and the customer may need to upgrade the Nutshell plan or consolidate pipelines before migration. Stage names and probabilities map directly, and we resolve the Party reference to the People or Organisation record created in the split step.

Capsule Cases track customer support or service issues linked to Parties. Nutshell has no native Case object on all plan tiers; on accounts without Cases available, we map Capsule Cases to People records tagged with 'Case' or to a dedicated custom field, preserving status, priority, assignee, and description. On Nutshell plans that include Cases, we map directly to the Nutshell Case object with status and priority aligned to Nutshell's available values. The mapping type depends on the destination account's plan tier, which we confirm during scoping.

Capsule Projects exist on Starter and above plans and link to Opportunities. Nutshell has no native Project object, so we flatten Capsule Projects into Tasks under the linked Nutshell Opportunity. Project name becomes the Task subject, milestones become Tasks with a milestone flag, and project status maps to Task status. Projects with no linked Opportunity are attached to the primary Party on the project. Workflow Automations, available only on Growth and above, are not migrated as code and are documented separately for the customer to rebuild.

Capsule custom fields are built via its data-tag system and require definitions fetched separately from the /fields/definitions endpoint per entity type (parties, opportunities, cases) before values can be correctly typed and mapped. List-type fields require option set resolution to cast raw values to Nutshell's picklist options. Note-type fields from Capsule may arrive as plain text without formatting when exported, so we flag this for the customer to review post-migration. We pre-create Nutshell custom fields before record import to ensure the target schema is ready.

Capsule Activities log email interactions, calls, meetings, and notes against Parties. Email and call activities map to Nutshell Tasks with the activity type and direction preserved. Meeting activities map to Nutshell Events with start time, end time, and location. Note activities attach to the People record as notes. Activity timestamps and assignee mapping carry forward. Nutshell's Import2 integration uses a sample-then-approve workflow where the customer reviews sample data before approving full migration, and we coordinate with Import2 for activity migration using the API-driven approach.

Tags in Capsule are flat labels applied to Parties, Opportunities, and Cases. We translate Capsule tag names 1:1 into Nutshell tags on the corresponding record. Nutshell's tagging model is per-record and flat, which aligns with Capsule's model without requiring transformation. Tags serve as the primary cross-object classification system in both platforms.

Capsule Users are assigned as owners of Parties, Opportunities, Cases, and Tasks. We map Capsule Users to Nutshell Users by email address, which serves as the dedupe and reconciliation key. Owner assignments on Parties and Opportunities migrate with the User reference resolved to the matching Nutshell User record. Users without a matching Nutshell User go to a reconciliation queue for the customer's admin to provision before record import resumes.

Milestones are sub-objects of Projects in Capsule representing time-bound deliverables. We map milestones to Nutshell Tasks with a milestone flag set, preserving the due date and completion status. Milestones without a parent Project are attached to the primary linked Opportunity or Party. This mapping is part of the Project flattening step and depends on the parent Project being mapped to Tasks under the linked Opportunity.