Migrate from Efficy CRM to Microsoft Dynamics 365 Sales

Efficy Companies map directly to Dynamics 365 Accounts. The Efficy company name becomes Account Name, the domain property becomes Website, and Industry maps to the Dynamics Industry picklist. We extract Companies first and load Accounts first in the migration sequence because Contacts and Opportunities carry foreign-key lookups to the parent Account (Efficy KCompany or equivalent). Account is created in Dynamics before any Contact batch begins so that the AccountId reference is satisfied at insert time.

Efficy Contacts map to Dynamics 365 Contact with the parent Company resolved to the AccountId lookup. Standard properties (name, email, phone, address) map to typed Contact fields; custom fields on Contact in Efficy map to custom fields on Contact in Dynamics. Multi-address records are flattened to the primary address unless the customer specifies a different strategy during scoping. We validate email format and uniqueness before insert.

Efficy Opportunities map to Dynamics 365 Opportunity with the parent Company resolved to AccountId and the primary Contact resolved to ContactId. The Efficy dealstage maps to Dynamics StageName, and pipeline assignments map to a Dynamics Sales Process or Record Type that we configure before migration. Closed-Lost reason and Closed-Won reason from Efficy custom properties become Dynamics LossReason and Win Reason fields.

Efficy stores calls, emails, meetings, and tasks as a single Activities object with a type discriminator field. Dynamics 365 separates these into Task (Call subtype), Event, and EmailMessage, each with a distinct schema. We apply a type-aware transform during migration: call activities become Task records with TaskSubtype=Call and duration preserved; meeting activities become Event records with StartDateTime and EndDateTime; emails become EmailMessage records with IsEmailIncoming flag; standalone tasks become Task records. The WhoId and WhatId lookups are resolved to the migrated Contact and Account or Opportunity respectively.

Efficy's project management module (Kanban views, milestones, nested tasks) has no direct equivalent in Microsoft Dynamics 365 Sales . We agree on the target approach during scoping — either the separate Dynamics 365 Project Service module (if the customer has or will acquire that license) or a SharePoint document library integrated with a custom Project entity in Dataverse. We preserve project structure, milestones, and task assignments as the migration deliverable; the entity and relationship configuration is a separate configuration step before or after data migration.

Efficy Tickets (status, priority, agent assignment, conversation history) map to Dynamics 365 Case if the destination org includes Service Cloud or Sales Enterprise/Premium. Custom ticket fields map to Case custom fields; conversation history migrates as threaded Case Comments or EmailMessages linked to the Case. If Service Cloud is not in scope, we agree on a custom entity approach during scoping and pre-create the schema before migration. We flag any Ticket with no resolution as open and preserve the original Efficy ticket ID in a custom field for cross-reference.

Efficy allows custom fields on all major objects (Company, Contact, Opportunity, Activities). During scoping we extract the full field schema per object — field names, types (text, picklist, numeric, date, checkbox), and picklist values — and pre-create the equivalent custom fields in Dynamics Dataverse before any data loads. Picklist values map directly; numeric and date fields map to typed Dataverse columns. We validate Dynamics field limits (maximum 500 custom fields per entity) before migration and flag any customer whose schema approaches the limit.

Documents attached to Companies, Contacts, or Opportunities in Efficy migrate to SharePoint document libraries integrated with the relevant Dynamics Account or Contact record, or as Notes with file attachments if SharePoint is not available in the destination org. We extract the document list from Efficy via the API, resolve the parent record reference, and create ContentDocumentLink records linking each document to the migrated Account, Contact, or Opportunity. Documents without a download URL are flagged in the reconciliation report for manual handling.

Efficy Users carry roles and assignments that map to Owner or Assignee fields in Dynamics. We extract distinct Efficy owners referenced on Contacts, Opportunities, and Activities and match by email against the Dynamics destination org's User table. Owners without a matching User go to a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Efficy users are excluded from the user count mapping but their historical assignments are preserved by mapping to an inactive Dynamics user record created for migration purposes.

Efficy Tags are object-level labels that map to Dynamics multi-select picklist fields on the relevant entity. We flatten the tag list per object, create a multi-select picklist field in Dynamics Dataverse, and populate it during the Contact and Opportunity import phases. The customer chooses whether to preserve all tags or consolidate to a top-N set during scoping.

Efficy automation rules, follow-up sequences, and workflow triggers do not export via the API or Import Wizard and cannot be delivered as Power Automate flows by automatic conversion. We document every active automation during discovery — trigger type, conditions, actions, and assigned owner — and deliver a written rebuild specification mapping each Efficy automation to a Power Automate flow or Dataverse workflow step. The customer's Power Platform team or a Microsoft partner rebuilds the automations post-migration.