Migrate from Simplero to Microsoft Dynamics 365 Sales

Simplero Contacts with subscription status active map to Dynamics 365 Contact. Contacts with a high-volume audience profile and no direct sales relationship may map to Dynamics 365 Lead instead if the customer prefers a lead-first intake model. We resolve this split during scoping using Simplero's tag profile and the customer's sales process description. The original Simplero contact ID is preserved in a custom field simplero_contact_id__c for reconciliation.

Simplero Tags are flat key-value labels applied to contacts. We migrate tags as either Dynamics 365 multi-select picklist fields (if tag cardinality is under 200 distinct values) or as Topic/TopicAssignment records (if the customer prefers a taxonomy approach). Tag preservation requires pre-creation of the custom field or topic schema in Dynamics 365 before import begins. We do not migrate segment membership as a native Dynamics concept; dynamic segments are converted to static lists or tag-based custom fields.

Simplero Segments are dynamic filter groups with criteria that do not have a direct Dynamics 365 equivalent. We export the segment criteria and member list during scoping, then create corresponding Dynamics 365 Marketing segments (if Dynamics 365 Marketing is licensed) or static contact lists that we update post-migration. The segment logic itself cannot migrate as an active rule.

Simplero Products (courses, memberships, coaching programs, digital downloads) map to Dynamics 365 Product2 records. Product type classification (course, membership, session) migrates as a custom field product_type__c on Product2. Pricing migrates to Standard Price Book entries. We create the price book in Dynamics 365 before product import so that PricebookEntry records have a valid reference.

Simplero Orders include product, price, date, payment gateway, and refund status. Historical order records map to Microsoft Dynamics 365 Sales Order if the customer needs order history as a CRM object, or to Opportunity records with Closed Won status if they prefer to treat historical purchases as opportunities. Refund flags map to a custom field refund_status__c. Payment gateway references do not migrate as Dynamics has no Simplero payment integration.

Simplero Members are contacts with active product access. We migrate member status as a custom field enrollment_status__c on the Dynamics 365 Contact, with a multi-select picklist of enrolled product names. If the customer uses course completion tracking, we create a custom object Course_Enrollment__c with a lookup to Contact, a lookup to Product, enrollment date, and completion status.

Simplero Deals are available only on the Skyrocket tier ($249/mo). We migrate Deals to Dynamics 365 Opportunity with the Skyrocket-to-Opportunity stage mapping defined during scoping. Deal value, owner, close date, and pipeline stage all map directly. If the customer never had Skyrocket access, no Deals exist to migrate and this step is skipped. Pipeline stage names vary by customer and require value mapping to Dynamics 365 stage picklist values.

Simplero Owners map to Dynamics 365 User records. We resolve owners by email match against the destination Dynamics 365 org. Any Simplero Owner without a matching Dynamics 365 User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Owner is required on Opportunity and is conditionally required on Contact based on the org's security model.

Simplero custom Contact Fields require pre-creation in Dynamics 365 before import. Field type mapping applies: text fields map to Text, numeric fields to Number or Decimal, date fields to Date, checkbox fields to Two Options. We create the custom field schema in a Dynamics 365 Sandbox for validation before production deployment. Custom fields without a pre-created destination are skipped with a gap report delivered to the customer.

Simplero Sites are no-code pages on the Simplero builder. Site page content does not migrate as a Dynamics CRM object. We preserve the slug structure for URL redirect mapping and deliver a slug inventory for the customer's web team to configure redirects in the destination hosting environment. The page content itself requires manual re-creation or a migration specialist for the no-code builder.