Migrate from Weave to Microsoft Dynamics 365 Sales

Weave patients map to Dynamics 365 Sales Contacts. The patient's primary location, contact preferences, and HIPAA consent flags migrate as custom fields on the Contact record. Phone numbers and email addresses transfer directly to the Contact phone and email fields.

Weave stores patient addresses per location. Each address pair migrates as a Dynamics 365 CustomerAddress record linked to the Contact, preserving address type (billing, shipping, home) and the associated location identifier from Weave. For multi-location practices, each clinic location creates a separate address entry with its own type classification and location reference, maintaining the full geographic context from the original Weave dataset.

Weave appointments map to Dynamics 365 Tasks or custom Dataverse Appointment entities. The appointment subject, scheduled time, and assigned staff member migrate as Task Subject, Due Date, and Owner respectively. Appointment status (confirmed, completed, no-show) maps to Task StatusCode values.

Weave call logs preserve call direction (inbound/outbound), duration, timestamp, and recording reference. These migrate as Dynamics 365 PhoneCall activity records with the Subject, Duration, and actual Start time populated from the Weave call log. Call recording URLs or file references transfer as notes attached to the PhoneCall activity, maintaining access to the original audio for audit and quality assurance purposes.

Weave text messages migrate as Email activities in Dynamics 365 Sales for audit trail purposes. The message body, timestamp, and direction transfer as Subject prefix ('SMS Incoming' or 'SMS Outgoing'), Description, and Created On. Alternatively, messages can land in a custom Dataverse SMSLog entity if configured.

Weave payment records have no direct Dynamics 365 Sales equivalent outside of the Sales module's Invoice entity. If the practice uses Dynamics 365 Sales for billing, payments map to Invoice records. Otherwise, payments migrate as a custom PaymentHistory custom entity on Dataverse linked to the Contact.

Weave staff members (dentists, hygienists, front desk) resolve to Dynamics 365 Sales SystemUser records by email match. Unmatched staff members are flagged before migration so the practice can create their Dynamics user accounts or assign records to a fallback owner.

Weave intake form data — medical history, insurance information, consent signatures — has no standard Dynamics 365 equivalent. We create a custom IntakeResponse Dataverse entity with fields for each intake question, linked to the Contact record via a lookup relationship.

Patient insurance carriers, policy numbers, group numbers, and coverage details from Weave migrate as a custom InsuranceDetail Dataverse entity. Fields include InsuranceCarrier, PolicyNumber, GroupNumber, EffectiveDate, and RelationshipToInsured, linked to the Contact.

Weave's automated appointment reminders and recall campaigns have no direct Dynamics 365 Sales equivalent. These records preserve as a custom RecallTask entity or migrate as Future-dated Tasks for reference, but the automated sending logic must be rebuilt using Power Automate or Dynamics 365 Sales Accelerator. The custom RecallTask entity approach preserves the scheduled reminder logic as data rather than automation, making it straightforward to rebuild the sending workflows within the Microsoft ecosystem.

Weave text and email templates migrate as Dynamics 365 Email Template records for manual reuse. The template body and subject transfer, but automated trigger logic (send on appointment confirmation, send 24 hours before) must be rebuilt in Power Automate flows.

Weave's automatic Google review request triggers have no Dynamics 365 Sales equivalent. Review request history migrates as a custom ReviewRequest entity linked to the Contact for reference, but the automated sending mechanism requires a separate rebuild. The migrated ReviewRequest records preserve request dates, patient links, and review platform identifiers for post-migration reconciliation and future workflow integration.