Migrate from Weave to HighLevel

Weave Contacts map directly to HighLevel Contacts. The phone number (Weave's primary identifier) maps to HighLevel's phone1 field. The contact's email maps to the email field and drives deduplication. Custom fields on Weave contacts migrate to custom fields on HighLevel Contacts.

Weave has no native Company object; the practice or organization name typically lives in the contact record. We extract this value and create a corresponding HighLevel Company record, then link it to the contact via the Contact-Company relationship. Unlinked contacts receive a placeholder Company record.

Weave Appointments (with date, time, duration, provider, and status) map to HighLevel Calendar events. The appointment title and patient name become the event title, original timestamps are preserved, and the assigned provider maps to the HighLevel user. Appointment status (confirmed, cancelled, no-show) maps to custom fields on the calendar event.

Weave Voicemails have duration, transcription, caller ID, and timestamp. The voicemail metadata (caller, duration, date, transcription) migrates as an activity log entry on the contact timeline in HighLevel. The voicemail audio file is preserved as a file attachment on the activity record if Weave's API exposes it.

Weave text messages (both sent and received, with full message body and timestamp) map to activity log entries on the contact in HighLevel. Direction (inbound/outbound) is preserved as the activity type. Original message timestamps are retained for conversation history continuity.

Weave Payments include amount, date, method, status, and related contact. HighLevel has no native payment object, so we create a PaymentRecord Custom Object with custom fields for amount, payment date, payment method, and status. The payment record is linked to the contact via a lookup relationship.

Weave's review module tracks review requests sent, review status, platform (Google, Facebook, etc.), and rating. We create a ReviewRecord Custom Object in HighLevel with fields for review source, rating, content, and request date. Reviews are linked to the originating contact record.

Weave tags on contacts (such as 'new patient', 'recare', or 'overdue balance') map directly to HighLevel tags. All tags applied to a Weave contact are applied to the corresponding HighLevel contact record during migration. HighLevel's tag-based segmentation and filtering work identically to Weave, so your team can use the same tag logic for workflows and contact views after go-live.

Weave staff members and providers map to HighLevel Users by email address match. Unmatched users are flagged before migration — the team either creates HighLevel accounts or assigns records to an existing fallback user. User permissions are destination-side configuration and not migrated.

Weave workflows (appointment reminders, follow-up texts) cannot migrate to HighLevel's Workflow engine because the two systems use entirely different automation architectures. We export the workflow definitions as a written rebuild reference. All automations must be reconstructed in HighLevel's Workflow Builder.

Weave email templates and messaging sequences do not migrate. HighLevel has its own template editor and workflow-based email/SMS sequences. We provide a template inventory export from Weave so your team can rebuild templates in HighLevel.

Weave call recordings are audio files stored in Weave. HighLevel supports file attachments on contacts and activities. We attempt to export call recordings via Weave's API and attach them to the corresponding activity record in HighLevel. If recordings are not accessible via API, we flag them for manual re-upload by the practice.