Migrate from Nurture to Microsoft Dynamics 365 Sales

Nurture Companies map to Dynamics 365 Accounts. The Nurture company name becomes Account Name, and the domain field maps to Website. We use Company Name as the dedupe key during import. Account must be inserted before any Contact that references it because the AccountId lookup on Contact is required in most Dynamics 365 configurations. If the Nurture account uses a single-company-per-contact model with no explicit Account, we create a placeholder Account using the Contact's company name and link all Contacts to it.

Nurture Contacts map to Dynamics 365 Contacts. We resolve the parent AccountId by matching the Nurture Company name to the Dynamics 365 Account Name dedupe key. Email address serves as an additional dedupe safeguard. Phone, job title, lifecycle stage property, and all standard Nurture contact properties migrate to typed Dynamics 365 Contact fields or custom fields pre-created in the destination org.

Nurture Deals map to Dynamics 365 Opportunities. The Nurture dealstage property maps to the Dynamics 365 StageName under the Sales Process assigned to the Opportunity's Record Type. Closed-Won and Closed-Lost dates from Nurture become Dynamics 365 CloseDate with stage value. We resolve the parent AccountId (from the linked Nurture Company) and OwnerId (from owner email match) before Opportunity insert.

Nurture pipeline names map to Dynamics 365 Opportunity Record Types. Each Record Type gets a corresponding Sales Process that whitelists the stage values from the Nurture pipeline, including stage order, stage probability, and stage category (Open, Won, Lost). If Nurture uses a single pipeline, we configure one Record Type with one Sales Process.

Nurture call engagements map to Dynamics 365 Task records with TaskSubtype set to Call. Call duration, disposition, and any notes migrate to custom Task fields. The parent Contact is resolved by email match against the migrated Contact records, and the parent Opportunity is resolved by deal name match against the migrated Opportunity records. Activity timestamp preserves from the Nurture engagement date.

Nurture email engagements migrate to Dynamics 365 EmailMessage records (body content) and a paired Task record (timeline entry). The EmailMessage WhoId points to the resolved Contact or Lead; the WhatId points to the related Opportunity or Account if one is associated. Subject and body text migrate as-is. We skip attachments if they exceed Dynamics 365 file size limits and flag them for manual transfer.

Nurture meeting engagements map to Dynamics 365 Event records. Start time, end time, location, and attendee list migrate. Attendees resolve to Contact or User records via email match and attach as EventRelation records. Meeting notes from Nurture become the Event Description field.

Nurture Task engagements (standalone tasks, not tied to calls or emails) migrate to Dynamics 365 Task records with Status, Priority, and ActivityDate preserved. Owner assignment resolves by Nurture owner email match to Dynamics 365 User. Completed status maps directly; open tasks retain due date and priority.

Nurture Owner records resolve to Dynamics 365 Users by email address. We extract every distinct owner email referenced on Contact, Company, Deal, and Activity records and match against the destination User table before any record migration begins. Any Nurture owner without a matching Dynamics 365 User goes to a reconciliation queue; the customer's admin provisions the missing User before record import resumes.

Nurture custom contact, company, and deal properties migrate to Dynamics 365 custom fields on Contact, Account, and Opportunity respectively. We create the custom field schema in Dynamics 365 before migration using the Dynamics 365 Web API or the customer's target org. Field type mapping follows standard equivalence: Nurture text becomes Dynamics 365 Single Line of Text; Nurture number becomes Decimal or Whole Number depending on precision; Nurture date becomes Date or DateTime in Dynamics 365.