Migrate from Ready_ to Microsoft Dynamics 365 Sales

Ready_ Contacts map to Dynamics 365 Sales Contacts with standard fields (fullname, emailaddress1, telephone1, address) migrated directly. The parent Account lookup requires the corresponding Company to be imported first. Custom properties on Ready_ Contacts (text, number, date, picklist types) map to custom fields on the Contact entity in Dataverse, which we pre-create during schema design. Null values in required Dynamics fields receive a placeholder string to prevent import failures; we flag these for the customer's admin to remediate post-migration.

Ready_ Company records map to Dynamics 365 Sales Account. The company domain in Ready_ becomes the Website field on Account, and company name maps to name. Firmographic fields (industry, number of employees, annual revenue) map to the corresponding standard Account fields. Related Contacts link via the AccountId lookup after the Account record is created. This is the first entity imported because all Contact records have an implicit dependency on a parent Account.

Ready_ Deals map to Dynamics 365 Sales Opportunities. The deal value migrates to estimatedvalue, expected close date to estimatedclosedate, and stage name to stageid via the Sales Process mapping. Owner assignment resolves from the Ready_ Team Member email to the corresponding Dynamics User. The deal's pipeline reference requires a mapping to a Dynamics Record Type and Sales Process that we configure during schema design. Closed-Lost and Closed-Won reason custom fields on the Deal map to corresponding custom fields on Opportunity.

Each named pipeline in Ready_ becomes a Dynamics 365 Sales Record Type on Opportunity, with a corresponding Sales Process that defines the available Stage values. The pipeline display order maps to the Sales Process sort order. Without this configuration step, Deals import with no valid stage assignment and are rejected by Dynamics validation rules.

Stage names from each Ready_ pipeline map to Stage values in the corresponding Dynamics Sales Process. Stage sequence order and probability percentage migrate from Ready_ to the Dynamics stage probability field. If a Ready_ pipeline has stages that have no equivalent in the destination Sales Process, we flag the gap and either create a catchall stage or route those Deals to a staging pipeline for manual review.

Ready_ Activities carry a type discriminator (call, email, meeting, task). We split them at migration time: emails map to Dataverse Email entities, calls to PhoneCall, meetings to Appointment, and tasks to Task. Each activity type carries the linked record reference (contact or deal), the timestamp, the owner, and the note body or disposition. Activity timestamps preserve the original UTC value to maintain timeline ordering in Dynamics. This split requires entity-level batch sequencing because each Dataverse activity type has its own API endpoint.

Ready_ Team Members are the owner entity for Deals and Activities. We extract every distinct Team Member ID referenced in the migration scope, resolve each to their email address and display name, and match by email against the existing Dynamics User table. Any Team Member without a matching Dynamics User is held in an owner reconciliation queue while the customer's admin provisions the User record. OwnerId references cannot be satisfied during import without this step, and Dynamics will reject records with invalid owner references.

Ready_ custom fields on Contacts, Companies, and Deals map to custom fields on the corresponding Dynamics 365 entity. We extract the field definition (type, label, picklist values) during scoping, create the matching Dataverse custom field with the same logical name during schema design, then migrate the values during the data phase. Text, number, date, and picklist custom fields migrate directly; any unsupported field types are flagged with a type-conversion recommendation.

Ready_ standalone Notes attached to Contacts or Deals migrate to Dynamics 365 Annotation entities (the Dataverse equivalent of notes). Note body, creation timestamp, and linked record reference transfer directly. File attachments on Notes migrate as Dataverse FileField values or become separate DocumentLocation records pointing to SharePoint if the customer's Dynamics environment has SharePoint integration enabled.