Migrate from Systeme IO to Microsoft Dynamics 365 Sales

Systeme.io contacts map directly to Dynamics 365 Sales Contacts. Email, phone, name, address, and custom fields transfer 1:1. The Contact must link to an Account (Company) — we resolve this by matching the contact's company name to the migrated Business record first.

Systeme.io Businesses map to Dynamics 365 Sales Accounts — the company-level record. We map company name, website, address, industry, and employee count. Parent-child business hierarchies in Systeme.io translate to Account.ParentAccountId relationships in Dynamics 365. Address details are stored in the Dynamics 365 composite address fields, preserving street, city, and country. Industry is mapped to the Dynamics 365 IndustryCode picklist.

Systeme.io contacts who have not made a purchase or converted through a funnel land as Dynamics 365 Sales Leads, not Contacts. We route all untagged or early-stage contacts to Lead so your Dynamics 365 lead scoring and nurturing workflows operate correctly.

Systeme.io products map to Dynamics 365 Sales Products with pricing details (price, description, product type). These feed into Opportunity Products for quote and order generation. Each product in Systeme.io becomes a Price List Item in Dynamics 365. Product pricing is linked to a Price List so Opportunities can reference current list prices during quote generation.

Systeme.io orders map to two Dynamics 365 objects: open orders become Opportunities with the order total as Amount and estimated close date; completed orders become actual Orders in Dynamics 365 with status 'Fulfilled'. This preserves both pipeline visibility and transactional history.

Systeme.io tags (e.g., 'webinar-attendee', 'course-buyer') have no native Dynamics 365 equivalent. We aggregate all tags into a custom text field (Tags__c) on Contact and Account, or create a custom Option Set if the tag vocabulary is standardized. This preserves segmentation data for reporting.

Each Systeme.io funnel becomes a separate Business Process Flow in Dynamics 365 Sales. Funnel step names map to Opportunity Stage values within that BPF. Stage-enter timestamps migrate as custom datetime fields on the Opportunity record for historical stage-timing analysis. The BPF stages are configured with the same names and order as the original funnel steps, ensuring a familiar pipeline view in Dynamics 365.

Email opens, clicks, and sends from Systeme.io campaigns migrate as Dynamics 365 Activities — emails stored as email activities, campaign enrollment as a Task with subject 'Campaign Enrollment'. Original timestamps and campaign names preserved. Email content itself migrates as Notes attached to the Contact record.

Form submissions and page view data from Systeme.io funnels migrate as Lead or Contact records with a custom field capturing the form name and submission source. The 'Lead Source' field in Dynamics 365 is used for top-level attribution (e.g., 'Landing Page — Free Trial').

Systeme.io automation rules (email sequences, tag triggers, date-based actions) do not have a migration path. We export a JSON definition of every automation rule including trigger conditions, time delays, and action sequence so your Dynamics 365 admin can rebuild equivalent flows in Power Automate.

Systeme.io custom fields migrate to Dynamics 365 custom fields prefixed with 'new_' per Dataverse convention. Custom fields are created in your Dynamics 365 solution before record migration begins. Data type mapping (text to string, number to whole number or decimal, date to datetime) is handled per field.

Systeme.io owner email addresses resolve against Dynamics 365 SystemUser records by email match. Unmatched owners are flagged with a report before migration — you either invite them to Dynamics 365 first or assign their records to a fallback owner. No record migrates without a valid OwnerId.