Migrate from eZnet CRM to Microsoft Dynamics 365 Sales

eZnet CRM Account records map directly to Dynamics 365 Account. Account name, address fields (street, city, state, postal code, country), phone, website, and industry classification transfer as typed fields. The Account is created first so that the AccountId lookup is satisfied for any dependent Contact imports. We use the Account Name and Email domain as dedupe keys during import to catch duplicates before they enter Dynamics 365.

eZnet CRM Contact records map to Dynamics 365 Contact with parent AccountId resolved at migration time. Standard fields (firstname, lastname, email, phone, mobile, title, department) transfer directly. Address fields migrate to the Contact address composite. We preserve the Account-Contact link by resolving the parent eZnet Account to the corresponding Dynamics Account GUID before Contact insert.

eZnet CRM Opportunity records map to Dynamics 365 Opportunity with AccountId and OwnerId resolved before insert. The opportunity name, amount, estimated close date, and pipeline stage name transfer to name, estimatedvalue, closerdatetime, and stagecode respectively. We capture the stage order and probability from eZnet and reconstruct them as Sales Process stage values in Dynamics 365.

eZnet CRM pipeline and stage configuration migrate as Microsoft Dynamics 365 Sales Processes with corresponding Stage values. Stage names, display order, and probability percentages transfer to stagecode and stepname in the Sales Process metadata. We configure a default Sales Process matching the primary eZnet pipeline, with additional Sales Processes created per pipeline if the source has multiple.

eZnet CRM Lead records map to Dynamics 365 Lead with status and source fields preserved. Lead status (New, Contacted, Qualified, Disqualified) maps to Lead.StatusCode with statecode set appropriately. We preserve lead score or rating if present in eZnet as a custom field on Lead. Lead records without a corresponding Account are imported as standalone Leads; those linked to an eZnet Account carry a note to convert to a Contact attached to the matched Account after migration.

eZnet CRM Activities span calls, emails, tasks, and events in a single object differentiated by an activity type field. We split these into separate Dynamics 365 records at migration time: calls become Task with TaskSubtype=Call, task-type activities become Task, event-type activities become Event with StartDateTime and EndDateTime set, and email-type activities become EmailMessage linked to a Task. We preserve the ActivityDate as the activity timestamp and resolve the Regarding (regardingobjectid) to the parent Contact or Account by matching on email and name.

eZnet CRM Document Library metadata (filename, file type, upload date, owner) migrates as Dynamics 365 Notes with a SharePoint document location link. We export the document metadata and create corresponding SharePoint document libraries within Dynamics 365's native SharePoint integration. Actual file blobs require separate file transfer handling; we flag this during scoping and recommend the customer upload critical documents to the SharePoint location post-migration or use a file migration tool for the blob transfer.

eZnet CRM custom fields on Accounts, Contacts, Opportunities, and Leads migrate as Dynamics 365 custom attributes. We capture the full field schema during discovery including data type, picklist values, and visibility settings, then pre-create the equivalent custom fields in the Dynamics 365 environment before data import begins. Text fields map to nvarchar, number fields to decimal or integer, date fields to datetime, and picklist fields to option sets with the original value labels preserved.

eZnet CRM user records with role-based assignments migrate by resolving the owner email to a Dynamics 365 User. We extract all distinct owner references from Accounts, Contacts, Opportunities, and Activities and match by email against the destination User table. Any owner without a matching Dynamics 365 User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive eZnet users are preserved as historical owner references on records migrated before their deactivation.

eZnet CRM Marketing Campaign records and associated campaign member data map to Dynamics 365 Campaign and CampaignResponse. Campaign name, status, budget, start and end dates transfer. Campaign member associations to Contacts preserve as CampaignMember records with Status values mapped to Dynamics 365 campaign member statuses. If the customer uses Dynamics 365 Marketing, we note that campaign flows and customer journeys do not migrate and require rebuild in Dynamics 365 Marketing.

eZnet CRM Inventory Items (Professional tier and above) map to Dynamics 365 Product2 records. Item name, SKU, unit price, stock level, and product description transfer to name, productnumber, price, quantityonhand, and description respectively. We create the Products before importing any Line Items or Opportunity Product associations so that the Product GUID is available at insert time.