Migrate from Weave to Salesforce Sales Cloud

Weave patient records map directly to Salesforce Contact. Every contact in Weave becomes a Contact in Salesforce with FirstName, LastName, Email, Phone, and address fields preserved. Contacts without a primary Weave location receive a default Account. Staff and provider records also migrate as Contacts.

Weave locations (dental offices, clinics, veterinary practices) map to Salesforce Account records, preserving the location name, address, and phone. Multi-location practices produce multiple Account records. Each Contact links to its primary Account via AccountId. Secondary location associations are stored as Account Contact Relationships.

Weave stores structured call and text records with direction, type, duration, disposition, and message content. Salesforce has no native equivalent for this depth of communication metadata. We create a custom Communication_Log__c object with fields for Direction__c, Type__c, Duration__c, Disposition__c, and Message_Content__c. Each log record links to the Contact via Weave_ID__c, a custom external ID populated from Weave's record identifier.

Basic call and text activity from Weave logs as Salesforce Tasks with Subject, TaskSubtype (Call or Text), Status, and OwnerId resolved by email match. Task.CallType captures inbound/outbound. Weave's disposition and duration data is stored in the custom Communication_Log__c object. The Task record provides standard Salesforce activity reporting against the Contact.

Weave appointments map to Salesforce Events with Subject, StartDateTime, EndDateTime, and Type. The appointment location field migrates as Location__c on the Event. Appointment description migrates as Event_Description__c since Salesforce Events have a 32,000-character description limit. Staff owner resolution uses email matching against Salesforce Users.

Payment and billing records from Weave migrate as a custom Payment__c object with Amount__c, Payment_Date__c, Payment_Status__c, and Payment_Type__c fields. Each payment links to the Contact via Weave_ID__c. Weave's payment status values map to Salesforce pick-list values. Recurring payment schedules require manual rebuild in Salesforce as Salesforce CPQ or a billing integration tool.

Review data migrates as a custom Review__c object with Rating__c (Number), Review_Date__c, Source__c, and Status__c fields. Weave's 'request' and 'received' status values map to Salesforce 'Sent' and 'Completed' via value mapping. The Weave review-gathering automation does not migrate — it must be rebuilt in Salesforce Flow as a separate project.

Weave staff and provider records resolve to Salesforce Users by email address. If a Weave user has no matching Salesforce User, the Contact record is assigned to a designated fallback User and flagged for admin review. Weave role and permission data cannot migrate — Salesforce profiles and permission sets must be assigned post-import.

Weave custom patient properties (communication preferences, patient IDs, insurance fields, referral sources) migrate as custom fields on the Contact object. Salesforce field names use the __c suffix and follow Salesforce naming conventions (no spaces, no special characters). The migration plan lists every custom property with its target field name, data type, and pick-list value mapping before data loads.

Weave file attachments on patient records, appointments, or communications re-upload to Salesforce Files linked to the relevant Contact or Event. File size limits apply (Salesforce default 25MB per file). Inline images in notes are extracted and re-hosted. The original Weave file name is preserved as ContentDocument.Title for traceability.

Weave notes on patient records migrate as Salesforce Notes (classic) or ContentNotes (Lightning). Rich-text formatting is preserved during conversion. Each note links to the Contact via the parent ID. Original Weave create dates are preserved as a custom Created_In_Weave__c datetime field for audit continuity.

Weave automations, sequences, text templates, and review-gathering workflows do not migrate. These are application-layer logic that cannot be extracted in a data migration. We export Weave workflow definitions as a reference document and provide a rebuild guide for Salesforce Flow. Practices should budget for Flow design as a separate workstream after data migration.

Weave email templates, text message templates, and notification logic cannot be exported in a data migration. Salesforce email templates and SMS templates must be rebuilt separately. We provide a template inventory from Weave as a starting point for the Salesforce admin or Flow builder.