Migrate from User.com to Microsoft Dynamics 365 Sales

Discovery and contact billing audit

We audit the User.com source portal across plan tier (Basic/Professional/Enterprise), contact count including chat visitors and push subscribers, custom properties, companies, deals, events, activities, and any export version indicators (f/t booleans, {} choice brackets). We cross-reference the in-app contact count with API-sourced counts to establish the accurate billing baseline. We pair this with a Dynamics 365 edition check: Professional ($65/user) covers most migrations; Enterprise ($105/user) is required if the customer needs advanced forecasting, Sales Acceleration, or Conversation Intelligence. The discovery output is a written migration scope with record counts and a Dynamics 365 edition recommendation.

Schema design and Dynamics 365 pre-configuration

We design the destination schema in Dynamics 365. This includes pre-creating custom fields (with Dataverse data types matched to User.com custom property types), configuring Account-Contact-Opportunity lookup relationships, setting up Sales Processes and stage values, and defining OptionSet values for migrated tags and choice fields. Schema is deployed via a solution package into a Dynamics 365 Sandbox environment for validation before production migration begins. We also coordinate with the customer's admin to configure security roles and flag any validation rules that need suspension during the load window.

Sandbox migration and reconciliation

We run a full migration into a Dynamics 365 Sandbox using production-like data volume. The customer's RevOps lead reconciles record counts (Contacts in, Accounts in, Opportunities in, Activities in), spot-checks 20-40 random records against the User.com source, and signs off the schema and mapping before production migration begins. Any field mapping corrections, lookup resolution failures, or data format issues surface here, not in production.

Owner reconciliation and User provisioning

We extract every distinct User.com Owner referenced on Contact, Company, Deal, and Activity records and match by email against the Dynamics 365 destination org's User table. Owners without a matching Dynamics 365 User go to a reconciliation queue. The customer's admin provisions any missing Users before record migration resumes, because OwnerId references are required on most standard entities.

Production migration in dependency order

We run production migration in record-dependency order: Accounts (from User.com Companies), Contacts (with AccountId resolved), Opportunities (with AccountId, OwnerId, and Sales Process resolved), Activity history (Tasks and Events via Dataverse bulk API with chunking and backoff). Custom fields and tag migrations run in parallel with their parent objects. Each phase emits a row-count reconciliation report before the next phase begins. We apply the Bool and DateTime normalization transforms during the extract phase, before data enters the load pipeline.

Cutover, validation, and automation rebuild handoff

We freeze User.com writes during cutover, run a final delta migration of any records modified during the migration window, then enable Dynamics 365 as the system of record. We deliver the automation and email template inventory document to the customer's admin team with recommended Dynamics 365 equivalents (Sales Automation, Power Automate, or manual workflow). We support a one-week hypercare window where we resolve any reconciliation issues. We do not rebuild User.com automations as Dynamics 365 workflows inside the migration scope; that is a separate engagement or an internal admin task.