Migrate your Sellsy data

Sellsy conflates Individuals and Companies into a single Contact model with a 'type' discriminator. Exports bundle both types together without a clean separation field. We split by the type attribute and map Individuals to Contacts and Companies to Accounts in the destination CRM, preserving all custom field values.

Corporations are the company-level object in Sellsy. The API exposes Corporation records via /corporations endpoints. We map Corporations to the destination's Company/Account object and handle the link between Corporation and Individual records as an association table during import.

Opportunities map cleanly to Deals in most destination CRMs. The Sellsy API supports create, update, and search endpoints for Opportunities with owner_id assignment available since API v2.29. Pipeline stage names are preserved as a custom field on the destination Deal object.

Sellsy invoices are first-class API objects with GET, POST, compute, and custom-fields endpoints. We preserve line items, discounts, taxes, and SmartTags. Invoice status (draft, sent, paid) is mapped to the destination invoice object lifecycle. Credit note associations are tracked via GET /invoices/{id}/credit-notes.

Orders track commercial transactions distinct from invoices. The Sellsy API supports SmartTags on orders. We map order records to the destination Order or Sales Order object, preserving product-line associations and custom fields.

Credit notes were added as a first-class API object in v2.86.0 with full CRUD, compute, validate, and SmartTag endpoints. We preserve the linked invoices reference and map credit note amounts to the destination as negative line items or as a credit memo object depending on the target schema.

Staff records represent Sellsy users and carry role/privilege information. We map Staff to the destination's User/Owner object, but access-control models differ significantly between CRMs. We preserve role names as a custom property on the destination User record and flag any staff without email addresses as non-migratable users.

Tasks are available in the Sellsy data model and can be exported via CSV and API. We map Tasks to the destination Task object and preserve assignee links. Due dates and task status are mapped as standard fields; custom task fields require field-level mapping against the destination's task schema.

Activities include appointments, calls, and logged interactions tracked against contacts and opportunities. We map these to the destination's Activity/Engagement log, preserving the linked Contact and Opportunity associations. Activity types are mapped to the destination's activity category taxonomy.

Products and services are managed in Sellsy's product catalog with pricing rules. The API exposes catalog entries and pricing matrices. We map Products to the destination Product or Item object and preserve price lists, descriptions, and tax codes.

SmartTags are Sellsy's tagging system for Invoices, Orders, and Credit Notes. They are not a first-class relational object in most destination CRMs. We map SmartTags as Tags on the respective transaction records and flag them as a tagging-layer artifact that may need taxonomy cleanup in the destination.

Sellsy supports custom fields on Invoices, Contacts, and Corporations via dedicated GET+PUT /custom-fields endpoints. Custom field types and labels vary by object. We inspect the custom field schema at scoping time and build a field-level mapping table against the destination object's equivalent custom field definitions.