Migrate from RAYNET CRM to Microsoft Dynamics 365 Sales

RAYNET Contacts with lifecycle stage set to unqualified or prospect status map to Dynamics 365 Lead. Contacts with a defined Account relationship and confirmed buyer status map to Dynamics 365 Contact attached to the corresponding Account. The split rule is defined during scoping against the customer's RAYNET lifecycle stage configuration. Original RAYNET lifecycle stage is preserved in a custom field raynet_lifecycle_stage__c on both Lead and Contact for audit and reporting continuity.

RAYNET Company records map directly to Dynamics 365 Account. The company name becomes Account Name, and the registered address maps to the Billing Address fields. We map the primary contact on the RAYNET Company to the corresponding Contact record in Dynamics and link it as the Primary Contact lookup on Account. Account is created before any Contact import so that the ParentAccount lookup is satisfied at the moment of Contact insert.

RAYNET Deal records map to Dynamics 365 Opportunity. The RAYNET dealstage property maps to Dynamics StageName via a stage mapping table we configure before import. Deal value maps to Amount, estimated close date to Estimated Close Date, and probability to Opportunity Stage Probability. Owner resolution uses email matching to the Dynamics User table.

Each RAYNET pipeline's stage names, probabilities, and order are extracted from the pipeline configuration during scoping. We configure a Dynamics Sales Process and stage probability matrix that matches the RAYNET pipeline structure. If RAYNET is on START or PROFESSIONAL (single pipeline), we create one Sales Process in Dynamics. If ENTERPRISE (multiple pipelines), each maps to a separate Record Type with its own Sales Process.

RAYNET multiple pipelines (ENTERPRISE tier only) map to Dynamics 365 Record Types on Opportunity, each with its own Page Layout and Sales Process so that stage values remain scoped per line of business. We extract the full pipeline configuration during scoping and flag any pipeline count mismatch against the Dynamics Sales Enterprise tier, which supports unlimited Record Types.

RAYNET call activity records map to Dynamics 365 Task with TaskSubtype = Call. Call duration, outcome, and any notes transfer to custom Task fields. ActivityDate is set to the original RAYNET timestamp to preserve timeline ordering. The WhatId on the Task points to the related Account or Opportunity using the cross-reference table built during the parent-record resolution phase.

RAYNET email activity records (subject, body, direction, timestamp) map to Dynamics 365 EmailMessage records linked to an Activity Task for timeline display. The EmailMessage body and subject transfer directly; attachments migrate as separate Note or Attachment records linked via the regardingobjectid lookup. We resolve the recipient and sender as Contact or Lead lookups using email address matching against the migrated contact set.

RAYNET meeting activity records map to Dynamics 365 Event. StartDateTime, EndDateTime, Location, and subject preserve. Attendee resolution maps RAYNET meeting participants to Dynamics EventRelation records pointing at the related Contact, Lead, or Account. We set the IsAllDayEvent flag based on the RAYNET all-day indicator if present.

RAYNET Sales Order records (Subject, Final Price, Status, Estimated Costs, Delivery Date, Shipping/Billing address) map to Microsoft Dynamics 365 Sales Order. If the destination org is configured with the standard Order entity, we use that; otherwise we create a custom Order table in Dataverse with matching fields. Status values map via a status mapping table configured before import.

RAYNET Quote records linked to Deals map to Dynamics 365 Quote. Validity dates, quote line items, and pricing transfer to Quote and QuoteLineItem records. We resolve the Pricebook2 reference before line item import. Quote PDFs stored as attachments in RAYNET migrate as ContentDocument records linked to the Quote via ContentDocumentLink.

RAYNET custom fields on Contact and Account extract via list export and map to typed custom columns in Dynamics 365 Dataverse. Field type mapping follows: text fields to Text, numeric fields to Number or Decimal, date fields to DateTime, checkbox fields to Two Option (boolean). GPS coordinates from RAYNET Map Analysis preserve as two custom Decimal fields (latitude__c and longitude__c) on the Account entity.

RAYNET Tags on Contacts and Deals migrate to Dynamics 365 multi-select picklist fields on the equivalent entity. We extract the distinct tag values during scoping, define the picklist options in the destination schema, and map each record's tag array to the corresponding picklist values during import.