Migrate from Sellsy to Salesforce Sales Cloud

Sellsy's Contact export bundles Individuals and Corporations in a single file with a type discriminator field. We split by the type attribute during pre-flight, routing type=individual to Salesforce Contact. Mobile phone, email, job title, and address fields map directly. We preserve any custom field values from the Sellsy custom-fields endpoint and map them to typed Salesforce custom fields on Contact.

Sellsy Corporation records map to Salesforce Account. The Corporation SIRENE number (when populated) maps to a custom Account field for regulatory cross-reference. We create Accounts before Contact imports so that the AccountId lookup is satisfied at Contact insert time. Account is also the parent of any related Credit Notes and Invoices.

Sellsy Opportunities map to Salesforce Opportunity with owner_id, pipeline stage, amount, and expected close date preserved. The Sellsy pipeline becomes a Salesforce Record Type and Sales Process that we configure in the destination org before migration. Closed-Won and Closed-Lost reasons from Sellsy custom properties migrate to custom Opportunity fields.

Sellsy Invoices migrate to Salesforce Invoice (if Financial Services Cloud is licensed) or a custom Invoice object we create in the destination org. Line items, discounts, taxes, and SmartTags transfer as Salesforce Tags on the Invoice record. Invoice status (draft, sent, paid) maps to a custom status picklist. Invoice is created before any related Credit Note to preserve the linked-invoice reference.

Sellsy Orders migrate to Salesforce Order with product-line details, quantities, and SmartTags preserved. Order status maps to Salesforce OrderStatus. If the destination org does not have Order Management enabled, we create a custom Order object with equivalent fields.

Credit Notes (first-class API object in Sellsy v2.86.0) map to a custom Credit Memo object in Salesforce with the linked invoice reference preserved. Credit note amount and reason transfer as typed fields. SmartTags on Credit Notes migrate as Salesforce Tags on the Credit Memo record.

Sellsy Staff records map to Salesforce User by email match. We extract every distinct staff_id and email from Sellsy Staff records and cross-reference against the destination Salesforce org's User table. Owners without a matching User go to a reconciliation queue for the admin to provision. Any duplicate staff names (same first and last name, different email) are flagged during pre-flight because Sellsy CSV exports do not deduplicate owner names.

Sellsy Tasks migrate to Salesforce Task with Status, Priority, ActivityDate, and assignee link preserved. Task assignment resolves via the Staff-to-User email lookup before migration.

Sellsy Activities (appointments, calls, logged interactions tracked against contacts and opportunities) map to Salesforce Task and Event records. Calls migrate as Task with TaskSubtype=Call. Appointments migrate as Event with StartDateTime, EndDateTime, and Location preserved. Activity timestamps preserve the activity timeline ordering in Salesforce.

Sellsy product catalog entries map to Salesforce Product2 with Standard Price Book entries created during import. ProductCode and pricing matrices transfer from the Sellsy catalog API.

Sellsy SmartTags are per-transaction labels on Invoices, Orders, and Credit Notes. We remap SmartTags as Salesforce Tags attached to the respective transaction records. Where the destination Salesforce org does not have Tags enabled for that object type, we create a custom multi-select picklist field on the transaction object to hold the original SmartTag values.

Sellsy custom fields on Invoices, Contacts, and Corporations migrate to typed Salesforce custom fields on the corresponding objects. We inspect the custom field schema via the Sellsy GET+PUT /custom-fields endpoints before migration and pre-create the Salesforce custom field schema in a Sandbox org for validation before production deployment.