Migrate from Sellsy to Twenty CRM

Sellsy's Contact export bundles Individuals and Companies under a single model with a type discriminator. We split by the type attribute during pre-flight extraction: type=individual records become Twenty Person objects. Mobile, email, job title, and address fields map directly. The original Sellsy contact ID is preserved in a custom field sellsy_id__c for cross-reference and delta reconciliation.

Sellsy Corporation records (company-type contacts) map to Twenty Company. The corporation's SIRENE-derived data (legal name, registration number, address) migrates to the corresponding Company fields. We preserve the sellsy_corporation_id__c for lookup resolution if the customer later needs to cross-reference historical records.

Sellsy Opportunities map to Twenty Opportunities with stage, amount, expected close date, and owner preserved. Note that Twenty does not currently provide an automated incremental numbering system for Opportunity IDs (raised in r/selfhosted as a v2.0 concern). We flag this during scoping and recommend the customer configures a naming convention before migration. Pipeline mapping requires stage translation from Sellsy pipeline stages to Twenty pipeline stages.

Sellsy Invoices have no direct equivalent in Twenty CRM's standard schema. We create a custom Invoice object in Twenty (or use custom fields on Opportunity) during pre-migration configuration, mapping invoice number, issue date, due date, line items, tax amounts, and SmartTags. The customer must confirm their preferred destination schema for financial records before migration begins.

Sellsy Orders track commercial transactions distinct from invoices. Depending on the customer's process, we map Orders to either a custom Order object in Twenty or to Opportunity Line Items on the linked Opportunity. Order status (draft, confirmed, shipped, cancelled) requires a picklist configuration in Twenty.

Sellsy Credit Notes (API v2.86.0+) link to original invoices and carry credit amounts. Twenty has no native credit note equivalent. We create a custom Credit Note object or custom fields on the linked Invoice record, preserving the linked invoice reference and credit note amount.

Sellsy product catalog entries map to Twenty Products with name, description, unit price, and SKU preserved. Pricing rules and matrix configurations are simplified to a single unit price unless the customer specifies a pricing complexity requirement.

Sellsy Staff records map to Twenty Users. We resolve by email match. Sellsy's privilege and role model differs from Twenty's workspace permissions; we map the active/inactive status and preserve the original Sellsy role label in a custom field for the customer's admin to translate into Twenty's permission set during workspace configuration.

Sellsy Tasks map to Twenty Tasks with due date, status, assignee (via Staff-to-User lookup), and description preserved. Task priority maps to Twenty's priority field. Recurring task configurations are flagged as not migratable and noted for manual rebuild if applicable.

Sellsy Activity records (calls, emails, appointments) map to Twenty Task records for calls and logged communications, and Event records for calendar-based meetings. We preserve the linked Contact and Opportunity references via the sellsy_id__c cross-reference and set the original timestamp to maintain the activity timeline ordering.

Sellsy SmartTags are tagging labels applied to Invoices, Orders, and Credit Notes. Twenty supports tags on most objects. We map SmartTags to Twenty Tags on the respective object records. If the destination uses a custom Invoice or Order object, tags migrate to that object's tag field. SmartTags without a matching taggable field are held for customer decision on custom field creation.