Migrate from Sellsy to Pipedrive

Sellsy's Contact export bundles Individuals and Companies without a clean separation key, requiring pre-flight type-based splitting. Once isolated, Sellsy Individual records map to Pipedrive Person with name, email, phone, address, and custom field values preserved. The Pipedrive Person.organization_id field is left null during initial import and resolved in a second pass once Sellsy Corporation records have been imported as Pipedrive Organizations.

Sellsy Corporation records map to Pipedrive Organization. The API exposes Corporations via /corporations endpoints. We map corporate name, address, SIRENE-enriched fields (if present), and custom fields. Pipedrive Organization is created before Person import so that the organization_id link resolves on insert rather than requiring a post-import update pass.

Sellsy Opportunities map directly to Pipedrive Deals with pipeline stage mapped to Pipedrive stage_name, amount mapped to weighted_value, close date mapped to close_date, and owner_id resolved to Pipedrive User via Staff email lookup. Closed-Lost and Closed-Won status migrate as Pipedrive stage values with probability preserved where populated.

Sellsy Invoices are first-class API objects with line items, discounts, taxes, and SmartTags. Pipedrive has no native invoice object. We export invoice records with all line items, totals, and status to a structured CSV reconciliation spreadsheet, create Pipedrive Notes attached to the related Deal with a reference to the original invoice number, and remap SmartTags to Pipedrive Deal tags. The customer configures a separate accounting integration (such as Pennylane, Indy, or Zettle) post-migration for live invoice management.

Sellsy Orders track commercial transactions distinct from invoices and support SmartTags. Pipedrive has no native order object. We export order records with product-line associations and status to a structured CSV, create Pipedrive Notes attached to the related Deal with order reference, and remap SmartTags to Deal tags. If the customer requires live order tracking post-migration, we recommend evaluating Pipedrive's built-in Products feature or a third-party order management integration.

Sellsy Credit Notes were added as first-class API objects in v2.86.0 with full CRUD, compute, validate, and SmartTag endpoints. We export credit note records with linked invoice references and amounts to a CSV reconciliation file, create Pipedrive Notes attached to the related Deal, and remap SmartTags to Deal tags. The linked invoice reference is preserved as a custom field value for audit traceability.

Sellsy Staff records represent users and carry role information. We map Staff to Pipedrive User by email address lookup. Sellsy's CSV export requires unique owner names for downstream imports; we detect duplicate Staff names during pre-flight and ask the customer to disambiguate in Sellsy before export. Pipedrive User provisioning (email invitation, role assignment) is a prerequisite for migration and is handled by the customer's admin before we begin record imports.

Sellsy SmartTags are labels applied to Invoices, Orders, and Credit Notes. They function as a per-transaction tagging layer with no relational object in Pipedrive. We remap SmartTags to Pipedrive Deal tags (since financial documents attach to Deals via our reconciliation notes) and to Pipedrive Organization tags where the SmartTag applies at the account level. If a customer has no Deals in Pipedrive, SmartTags are dropped unless the customer requests a custom field creation to hold them.

Sellsy Products and services in the catalog with pricing rules map to Pipedrive Products. The Sellsy API exposes catalog entries and pricing matrices. We map product name, SKU, pricing, and unit to Pipedrive Product with standard pricing. If Sellsy uses pricing tiers or volume-based pricing, we map the base pricing to Pipedrive and document the tier structure for the customer to configure in Pipedrive's product pricing editor.

Sellsy Tasks export via CSV and API with assignee links and due dates. We map to Pipedrive Activity records of type Task with subject, due_date, marked_done (from status), and assignee resolved via Staff-to-User email lookup. Recurring task patterns do not migrate as automation; we document the recurrence rule as a Note so the customer's admin can configure Pipedrive's workflow automation post-migration if needed.

Sellsy Activities include appointments, calls, and logged interactions tracked against contacts and opportunities. We map call activities to Pipedrive Activity with type = Call and disposition preserved in a custom field; meeting activities map to type = Meeting with start and end timestamps; logged interactions map to Pipedrive Note. The linked Contact and Opportunity references migrate as Pipedrive Person and Deal lookups. Pipedrive's import API marks updated_at and created_by as read-only and cannot be populated from external data; activity timestamps are set to the original Sellsy timestamp where supported.

Sellsy custom fields on Invoices, Contacts, and Corporations are accessible via GET+PUT /custom-fields endpoints. We inspect the custom field schema at migration start, create equivalent Pipedrive custom fields (with matching or closest-approximated field types) before import, and map values during record migration. Sellsy custom field labels and API names are preserved in the mapping document for audit traceability. Pipedrive's custom field type restrictions (e.g., no multi-select beyond 40 options) may require type coercion that we document and the customer approves before import.