Migrate from Sellsy to Microsoft Dynamics 365 Sales

Sellsy Contacts with type discriminator set to 'individual' map to Microsoft Microsoft Dynamics 365 Sales Lead. The Sellsy contact firstname, lastname, email, phone, and address fields map to the corresponding Lead fields. Any lead score or custom scoring property from Sellsy maps to a custom Lead field for audit. We use the type discriminator in the Sellsy export to separate Individuals from Corporations before creating any destination records.

Sellsy Contacts marked as 'individual' who have an associated Corporation in Sellsy map to Microsoft Dynamics 365 Sales Contact tied to the target Account. The Corporation reference in Sellsy resolves to the AccountId on the Contact record at insert time. Contacts without a Corporation reference in Sellsy create standalone Contacts in Dynamics 365, though we flag this for the customer's admin to attach to an Account post-migration if hierarchical account structure is desired.

Sellsy Corporation records map directly to Microsoft Microsoft Dynamics 365 Sales Account. The corporation name, SIRENE/SIRET number (if populated), address, website, and industry fields map to Account fields. Account is created before any Contact import so that the AccountId lookup is satisfied at Contact insert. We preserve any Sellsy custom fields on Corporation as custom fields on Account.

Sellsy Opportunities map directly to Microsoft Dynamics 365 Sales Opportunity. The opportunity amount, probability, expected close date, and pipeline stage map to estimatedvalue, closeprobability, estimatedclosedate, and stagecode respectively. Sellsy's pipeline and stage names map to a Microsoft Dynamics 365 Sales Process and stage category. OwnerId is resolved via email match against the User table after owner deduplication. The parent AccountId is resolved via the linked Corporation reference in Sellsy.

Sellsy Invoices have no native equivalent in standard Microsoft Dynamics 365 Sales Professional or Enterprise. We create a custom SellsyInvoice table in Dataverse with fields matching the Sellsy invoice schema (invoice number, issue date, due date, line items, taxes, total, status, SmartTags). Each line item becomes a related SellsyInvoiceLine record. The linked Sellsy Contact (as ContactId) and Corporation (as AccountId) are preserved. The customer decides whether to keep this as a read-only archive or extend it with Microsoft Dynamics 365 Sales views and Power BI reporting.

Sellsy Orders map to a custom SellsyOrder table in Dataverse, mirroring the structure of the SellsyInvoice custom table. Order status (draft, confirmed, shipped, cancelled) is preserved as a status field. SmartTags on Sellsy Orders map to the custom SmartTags field on the SellsyOrder record. Microsoft Dynamics 365 Sales does not have a native Sales Order object in the standard Sales module without the Order Management addon, so the custom table approach provides the cleanest data preservation without requiring additional licensing.

Sellsy Credit Notes are the least portable object in this migration because they are accounting documents with a specific credit-to-invoice relationship. We create a custom SellsyCreditNote table in Dataverse with fields for credit note number, issue date, linked invoice reference, credit amount, and status. The SmartTags field carries the original Sellsy SmartTags. Microsoft Dynamics 365 Sales does not have a native credit note object; the custom table approach is the standard recommendation for companies that need to retain full accounting history from Sellsy.

Sellsy SmartTags applied to Invoices, Orders, and Credit Notes have no native equivalent in Microsoft Dynamics 365 Sales . We create a single custom string field SellsyTags__c on each of the three custom Dataverse tables to carry the comma-separated SmartTag values from Sellsy. Tags are not parsed into a multi-select picklist because the set of possible tags is unbounded and may vary by document type. The customer can request Power Automate to parse and re-apply tags to native Dynamics fields post-migration if needed.

Sellsy Products and Services map directly to Microsoft Microsoft Dynamics 365 Sales Product2 records. The product name, SKU (sellsy_sku field), description, unit, and pricing information map to the corresponding Product2 fields. Standard Price Book entries are created during import. Any pricing rules from Sellsy's product catalog are noted in the field map for the customer to reconfigure in Microsoft Dynamics 365 Sales Price Lists.

Sellsy Staff records map to Microsoft Microsoft Dynamics 365 Sales User records, resolved by email match. Owner deduplication is the critical pre-flight step: Sellsy's CSV export does not deduplicate owner names, so multiple staff members sharing a first-last name combination collapse to one user in the destination. We detect duplicates during pre-flight, ask the customer to either disambiguate in Sellsy or provide a unique identifier field, and proceed only when every Staff record has a unique email address for User lookup. Inactive or archived Sellsy staff map to inactive Users in Dynamics with the original role preserved in a custom field.