Migrate from Insider to Microsoft Dynamics 365 Sales

Insider user profiles with a lifecycle stage of sales qualified lead, opportunity, customer, or evangelist map directly to Microsoft Dynamics 365 Sales Contact. The email address serves as the primary dedupe key. Standard profile attributes (firstname, lastname, email, phone) map to Contact fields directly. Custom user attributes from Insider are mapped to custom Contact fields that we pre-create in the Dynamics 365 Dataverse schema before migration. The primary email address is used as the correlation key to resolve lookups from other migrating objects.

Insider user profiles with a lifecycle stage of subscriber, lead, or marketing qualified lead, and profiles with no associated opportunity, map to Microsoft Dynamics 365 Sales Lead. We apply a split rule during scoping using the lifecycle_stage and hs_lead_status properties, with the original Insider lifecycle stage preserved in a custom field insider_original_lifecycle__c on both Lead and Contact for audit and reporting continuity. The split is run as a pre-transform before any data is loaded into Dataverse.

Insider Company records map to Microsoft Dynamics 365 Sales Account. The company domain becomes the Account Website field and is used as the dedupe key during import. Account must be created before Contact import so that the AccountId lookup is satisfied at the moment of Contact insert. We use Dynamics 365 Dataverse bulk upsert with Account as the parent anchor entity to resolve the dependency chain before child record imports begin.

Insider segments defined by attribute rules and event conditions are exported as member lists plus the segment rule definition as metadata. In Microsoft Dynamics 365 Sales , we recreate segment membership as static Contact Views for frequently used audience groups, and we deliver an Advanced Find query definition file that reproduces each dynamic segment logic. Views are assigned to the relevant Business Unit and shared with appropriate Teams. Segment rule definitions that require event conditions are documented as Power Automate trigger criteria since Dynamics 365 Advanced Find does not support behavioral event conditions natively.

Insider user tags stored as string arrays per profile are exported and mapped to a Microsoft Dynamics 365 Sales custom multi-select picklist field on Contact. If the customer licenses Microsoft 365 Copilot for Sales, tags can alternatively be mapped to Copilot's CRM highlights or to Microsoft 365 Group labels. The mapping strategy is confirmed during scoping. Tags that represent content categorization are documented for potential use as Microsoft Dynamics 365 Sales Topic assignments.

Insider static Lists (collections of user IDs not defined by segment rules) export with user ID and list ID. We create Microsoft Dynamics 365 Sales Contact Views named after the original List, or we create a custom ListMember entity with a lookup to Contact if the customer requires programmatic list management in Dynamics 365. The choice depends on the customer's intended use of static lists post-migration.

Insider Product catalog data including sku, name, price, category, images, and custom attributes maps to Microsoft Dynamics 365 Sales Product2 records. ProductCode maps from Insider's hs_sku. We create Price List records and Price List Items during migration so that migrated Deals reference active pricing. If Insider's product catalog includes inventory quantities, those map to Dynamics 365 Inventory Management if the customer also uses Dynamics 365 Supply Chain Management.

Insider transaction records (order_id, total, currency, timestamp, items) map to Microsoft Dynamics 365 Sales Order (or Invoice depending on the order lifecycle stage in Insider). Line items map to SalesOrderDetail records. We resolve the Contact and Account references at migration time, and currency codes are mapped to Dynamics 365 TransactionCurrency records. Historical orders that are closed in Insider are imported as Invoices; open orders are imported as SalesOrders.

Insider behavioral events (page views, purchases, cart actions, custom events) have no direct Microsoft Dynamics 365 Sales equivalent since Dynamics 365 does not include a native CDP layer. We create a custom Activity entity in Dataverse called insider_event__c with fields for event_name, event_timestamp, event_parameters (JSON), and a lookup to the Contact record. Events are migrated via Dataverse bulk upsert, chunked at 10,000 records per batch with exponential backoff on throttling responses. Customers who require real-time event ingestion post-migration are directed toward Dynamics 365 Customer Insights or Azure Event Hubs as a long-term event infrastructure.

Insider Journeys are multi-step event-driven workflows with entry triggers, conditional gates, channel steps, and exit conditions. Insider provides no API to export Journey definitions, so we cannot migrate them mechanically. During discovery, we perform a Journey audit: we document every active Journey in a structured format (trigger type, conditions, steps, channel actions, exit criteria) and deliver this as a handoff document. The customer's Dynamics 365 admin or a Microsoft partner rebuilds Journeys using Power Automate triggers, Microsoft Dynamics 365 Sales Copilot workflows, or Sales Automation rules depending on the license tier. This is explicitly not a code migration; it is a documented manual rebuild scope.