Migrate from LeadPrime to Microsoft Dynamics 365 Sales

LeadPrime Lead records require a conversion decision at migration time. Leads with a qualified status, assigned owner, and associated company data map to Dynamics 365 Contact tied to an Account. Leads with early-stage status and no Account association map to Dynamics 365 Lead. We compute the split using LeadPrime's status and owner fields during the transform phase, preserving the original LeadPrime status in a custom field lpi_original_status__c on both Lead and Contact for audit trail and reporting continuity.

LeadPrime Contact records map directly to Dynamics 365 Contact. Standard fields (full name, email, phone, address) map to Contact entity attributes. The OwnerId resolves via email match to a Dynamics 365 User. Where LeadPrime Contacts are linked to Companies, we map the company to a pre-created Account and set the parent AccountId on Contact before insert to satisfy the lookup dependency.

LeadPrime Company records map to Dynamics 365 Account. Company name becomes Account Name, industry maps to Industry picklist, and company size maps to NumberOfEmployees or a custom field depending on the source field precision. Address fields map to Address composite fields on Account. The Account is created before Contact records that reference it so the AccountId lookup is satisfied at insert time.

LeadPrime User records map to Dynamics 365 User by email address. We extract all distinct user IDs referenced as owners on Lead, Contact, Company, and Activity records and resolve each to a Dynamics 365 User. Any LeadPrime owner without a matching Dynamics 365 User is placed in a reconciliation queue; the customer's admin provisions the missing Users before record migration proceeds.

LeadPrime pipelines map to Microsoft Dynamics 365 Sales Processes and Opportunity Record Types. We export the full pipeline topology (stage names, sequence, probability values) from LeadPrime and recreate it in Dynamics 365 as a Sales Process with matching stage values and probabilities. If the customer uses multiple LeadPrime pipelines, each becomes a separate Record Type on Opportunity.

LeadPrime Round Robin, Blind, Shark Tank, and Hybrid distribution rules are platform-specific configuration with no direct Microsoft Dynamics 365 Sales equivalent. We document the full rule definitions during scoping (rep assignments, capacity caps, territory filters, routing priority order) and deliver a written configuration guide for rebuilding them in Dynamics 365 using Power Automate or Dynamics workflow rules. The migration itself does not replicate the routing logic as functional code.

Custom fields on LeadPrime Leads, Contacts, and Companies are mapped to typed Dynamics 365 fields. We read the full field list during discovery, map each to a matching Dynamics 365 attribute (or pre-create a custom field with __c suffix), and flag any LeadPrime field types with no direct Dynamics equivalent for the customer to resolve during schema review. All custom field mappings are validated in a Sandbox migration before production.

LeadPrime tags migrate as flat label strings. Where the customer uses tags as a primary segmentation mechanism, we map them to a Dynamics 365 multi-select picklist or a text field depending on tag count and the Dynamics 365 field type strategy. Tags used for content or routing classification are documented separately for the customer to decide whether Power Automate triggers are appropriate replacements.

LeadPrime activity records (calls, emails, notes) map to Dynamics 365 Task, EmailMessage, and Note entities. Call activities migrate as Task with TaskSubtype=Call and CallDurationInSeconds preserved. Emails migrate as EmailMessage records linked to the parent Contact or Lead. Notes migrate as Note records attached via ContentDocumentLink to the parent record. All ActivityDate values preserve the original timestamp to maintain the activity timeline sequence.

LeadPrime Lead Finder Credits are a billing token tied to the platform's credit economy and have no data equivalent in Microsoft Dynamics 365 Sales or any other CRM. We record the credit balance at migration cutover and flag it for the customer to download separately for financial records. Any enrichment results already written to Lead records (verified emails, phone numbers) are migrated as part of those records.