Migrate from Regal.io to Microsoft Dynamics 365 Sales

Regal Contacts map directly to Dynamics 365 Contact. Every Regal Contact record requires a phone number validation step before migration: we filter the export for phone_number presence and flag any Contact without one as non-contactable in a custom field contactable_regal__c. Email, name, and address attributes map to standard Contact fields; custom profile attributes (tenant-specific) map to custom fields on the Contact entity with a regal_ prefix. We resolve the parent AccountId by matching Regal's company association to a Dynamics Account before Contact insert.

Regal's custom attribute schema varies by tenant. We extract the full attribute list from Regal's API before migration, classify each by data type (string, number, boolean, date), and provision matching custom fields on the Dynamics Contact entity via Dataverse. String attributes with enumerated values map to Picklist or OptionSet fields; multi-value attributes map to MultiSelect OptionSet. The customer reviews the attribute schema during scoping to confirm field names and data types before provisioning.

Regal's Contact records reference a company association that maps to a Dynamics Account. We extract all unique company names from Regal Contacts, create Account records in Dynamics, then backfill AccountId on Contact during the Contact import phase. Company-level attributes (industry, size tier, domain) map to standard Account fields or custom fields if the schema requires it.

Regal call events migrate to Dynamics Task with TaskSubtype=Call. Call duration, disposition code, recording URL (if available in Regal's retention policy), and outcome data transfer to custom Task fields (call_duration_seconds__c, call_disposition__c, recording_url__c). Activity timestamps preserve the original Regal event timestamp for timeline ordering. We batch these via Dynamics Bulk API to handle volumes over 100,000 call records.

Regal SMS message events migrate to Dynamics ActivityPointer records with a custom sms_direction__c flag (inbound/outbound) and sms_body__c for the message content. We use Email for the activity type because Dynamics does not have a native SMS activity object without third-party ISV add-ons; the sms_body__c field preserves the full message text. Thread continuity across Regal and Dynamics is not guaranteed because Dynamics SMS threading is ISV-dependent.

Regal email thread events migrate to Dynamics Email records linked to the Contact. The email direction (inbound/outbound), subject, body, and timestamp transfer to standard Email fields. Attachments migrate as Annotation records or Note attachments. If Regal's email integration uses a connected inbox, thread association maps via the contact's email address match.

Regal's general behavioral events that are not call, SMS, or email (web engagement, stage changes, custom event types) migrate as Note records on the Contact with a custom event_type__c field identifying the original Regal event type. This preserves the behavioral context in the Contact timeline without requiring a custom event entity in Dynamics. The customer reviews the event type taxonomy during discovery to confirm which events carry business value.

Regal Campaigns define outbound programs with list selection, cadence goals, and contact counts. These map to Dynamics 365 Campaign with CampaignType, BudgetedCost, and actualcost fields. Campaign membership (which Contacts were targeted) migrates as CampaignMember records linked to the Contact. Cadence logic and list-refresh rules are platform-specific and documented separately for Power Automate rebuild; they do not migrate as executable automation.

Regal AI Agent configurations—voice scripts, decision trees, persona settings, and handoff logic—are tied to Regal's proprietary runtime and are not exportable via API or UI. We explicitly exclude Agent logic from migration scope. We do export call outcome data, transcript availability flags, and Journey trigger conditions so the business context is preserved for manual rebuild in Dynamics with Power Virtual Agents or third-party voice AI.

Regal's branded caller ID (CNAM) carrier registration details export as a configuration record. We document the carrier, number range, and registration status so these can be re-registered in Dynamics' native phone number management or a third-party CNAM service post-migration. Microsoft Dynamics 365 Sales does not have a native branded caller ID feature; this requires a telecom add-on.

Regal's live integrations with Segment, HubSpot, Salesforce, Braze, and Iterable define which contacts are synced and how. We document active integration endpoints, sync frequency, and data flow direction so the migration plan includes re-establishing equivalent connections in Dynamics. Segment and HubSpot connections typically re-route to Dynamics via native Dataverse connectors; Braze and Iterable require custom API integration or a middleware layer.