Migrate from Sellsy to Freshsales

Sellsy Contacts of type Individual map to Freshsales Contact. We split the combined Sellsy Contact export by the type discriminator before migration, ensuring Individual records route to Contact and Corporation records route to Account. Email serves as the dedupe key. Custom fields on Sellsy Contacts migrate to Freshsales Contact custom fields. Any Sellsy Contact without an email address is held for manual review because Freshsales requires email for Contact creation.

Sellsy Corporation records map to Freshsales Account. The Corporation name becomes Account Name; the SIRENE-derived fields (if populated) can be mapped to custom Account fields for French regulatory teams that need to preserve that data. Account is created before any Contact import so that the Account Lookup on Contact is satisfied at insert time.

Sellsy Opportunities map to Freshsales Deals. The Opportunity stage maps to Freshsales Deal Stage, and the pipeline assignment maps to a Freshsales Sales Process or Record Type. OwnerId resolves via Staff email matching to Freshsales User. Closed-Lost and Closed-Won reasons from Sellsy custom fields become Deal custom fields in Freshsales.

Sellsy Invoices do not have a direct Freshsales equivalent. We map Invoice records to Freshsales Deals with the invoice number stored in a custom field, line items mapped as Deal Product line items, and the invoice status (draft, sent, paid) stored as a custom status field on the Deal. For customers with high-volume invoicing needs, we recommend a separate accounting tool post-migration and treat Invoices as historical records only.

Sellsy Orders map to Freshsales Deals with Order status stored in a custom field and order line items as Product line items on the Deal. SmartTags on Sellsy Orders migrate to Freshsales Labels on the corresponding Deal. Orders with a linked Invoice reference that has already been migrated inherit the Deal created from that Invoice to avoid duplicate Deal creation.

Sellsy Credit Notes map to Freshsales Deals with a Credit Note custom type field and the original linked Invoice reference preserved as a custom field. Amount fields migrate directly. Credit Notes are flagged as a financial document type for the customer's accounting team to reconcile post-migration.

Sellsy Staff records map to Freshsales User. We match by email address. Any Staff record without a matching Freshsales User goes to a reconciliation queue for the customer's admin to provision the User before record import resumes. Role and privilege information does not migrate because Freshsales role-permission models differ structurally from Sellsy's privilege model.

Sellsy Tasks map to Freshsales Tasks with Status, Priority, Activity Date, and Owner preserved. Task assignment migrates by resolving Sellsy Staff owner_id to Freshsales User via email matching. Tasks linked to Contacts, Corporations, or Opportunities carry the corresponding Freshsales lookup IDs after parent-record resolution.

Sellsy Activity records for calls map to Freshsales Tasks with TaskSubtype = Call and call duration preserved. Meeting and appointment activities map to Freshsales Events. The linked Contact and Opportunity references resolve via email dedupe on Contact and Deal name matching on Opportunity before the activity insert.

Sellsy Products map to Freshsales Products with pricing rules preserved. ProductCode from Sellsy maps to Freshsales Product SKU. Price list entries map to Freshsales Price Books. Products are imported before Deals so that line item Product references resolve correctly at Deal import time.

Sellsy SmartTags on Invoices, Orders, and Credit Notes map to Freshsales Labels on the corresponding Deal. SmartTags on other objects map to Label fields on the respective entity. Where Freshsales does not have a label field for the target object, SmartTags are stored in a custom multi-select text field. The customer chooses the strategy during scoping.

Sellsy custom fields on Contacts, Corporations, Invoices, and Orders map to Freshsales custom fields on the corresponding entity. We inspect the Sellsy custom field schema via the /custom-fields API before migration and pre-create matching Freshsales custom fields with appropriate field types (text, number, date, picklist, checkbox). Field-level validation rules in Freshsales may require adjustment if they conflict with data patterns from Sellsy.