Migrate from Sellsy to Nutshell

Sellsy exports Individuals and Corporations bundled in a single Contact export with a type discriminator field. We split on that discriminator before writing to Nutshell. Individual contacts map to Nutshell Person records with name, email, phone, and address fields preserved. The owner_id from Sellsy maps to Nutshell ownerId via email lookup against the Nutshell User table. Custom field values on Sellsy Contacts migrate to the Nutshell customFields dict on Person. Any Sellsy Contact without a type discriminator is flagged for manual review before migration.

Sellsy Corporation records map to Nutshell Account with company name, industry, website, and address fields preserved. The Corporation SIRENE number (if populated) migrates to a custom Account field. OwnerId resolves via email match to Nutshell User. Custom field values on Sellsy Corporations migrate to the Nutshell customFields dict on Account.

Sellsy Opportunities map to Nutshell Opportunities with deal name, amount, expected close date, and pipeline stage preserved. The pipeline in Sellsy maps to Nutshell's single customizable pipeline; if the customer has multiple Sellsy pipelines, we consolidate into one Nutshell pipeline with a custom field to track the original pipeline source. Stage names and probabilities migrate as stage labels and numeric weights. Closed-Lost and Closed-Won status map to Nutshell's loss and won stage values.

Sellsy SmartTags on Opportunities have no direct equivalent in Nutshell. We create a text or multi-select custom field on Nutshell Opportunity during pre-flight and populate it with the SmartTag values from the source Opportunity. SmartTags are not a native tagging layer in Nutshell, so this is a best-effort field mapping rather than a native tag migration.

Sellsy Product catalog entries map to Nutshell Products with name, SKU (hs_sku equivalent), unit price, and product description preserved. Products are migrated before Opportunities so that Opportunity line items can reference the correct Product records at import time.

Sellsy Tasks map to Nutshell Tasks with task name, description, assignee (via owner email to User lookup), due date, and status preserved. Sellsy's subtask hierarchy (if used) is flattened into individual Tasks with a custom field tracking the parent task reference, because Nutshell does not support a native subtask object.

Sellsy Activity records split by type: calls and meetings map to Nutshell Tasks with a task type discriminator; logged email interactions and general notes map to Nutshell Notes linked via ContentDocumentLink to the parent Person, Account, or Opportunity. The linked Contact and Opportunity references from Sellsy resolve to Nutshell IDs for the WhoId and WhatId equivalent fields. Activity timestamps preserve to maintain the timeline ordering that sales reps rely on.

Sellsy Staff records map to Nutshell Users by email match. The customer's Nutshell admin provisions Users before migration begins. Sellsy role and privilege metadata cannot map directly to Nutshell's access-control model because the two platforms enforce permissions differently. We preserve the Sellsy role label in a custom field on the Nutshell User record for audit purposes.

Sellsy Invoices are financial documents with no equivalent object in Nutshell. We do not migrate Invoices, Orders, or Credit Notes. We export a written inventory of outstanding Invoice amounts, linked line items, SmartTags, and payment status for the customer's accounting team to handle manually or in a dedicated accounting tool. SmartTags on invoices are listed in the inventory so the team can recreate them in the new system if needed.

Sellsy Orders are commercial transaction records distinct from invoices with no equivalent in Nutshell. We do not migrate Orders. We include the full order list with product lines, quantities, amounts, and SmartTags in the written financial inventory delivered to the customer.

Sellsy Credit Notes (API object since v2.86.0) have no Nutshell equivalent. We do not migrate Credit Notes. The written inventory covers outstanding Credit Note amounts and linked invoice references so the customer's accounting team can reconcile manually.