Migrate from m-savvy to HighLevel

M-savvy Contacts migrate to GoHighLevel Contacts with all standard fields preserved including name, email, phone, address, and lifecycle stage properties. We resolve the contact owner assignment using m-savvy Owner email matching to GoHighLevel user email. Custom contact properties discovered via API inspection map to GoHighLevel custom fields on the Contact object. Any m-savvy contact with no email is flagged for manual review because GoHighLevel uses email as a primary deduplication key.

M-savvy Account records representing organizations link to multiple Contacts. We map each Account to a GoHighLevel Location record and attach all related Contacts to that Location by ID resolution. Industry, size, and billing address fields from m-savvy migrate as Location custom fields. If GoHighLevel is configured without Locations enabled, Account data flattens into Contact address fields with a note in the reconciliation report.

M-savvy Deals migrate to GoHighLevel Opportunities. Deal amount, close date, stage, and probability transfer directly. The dealname field maps to the Opportunity name. We flag any Deals without a linked Account or Contact because GoHighLevel Opportunities must associate with a Contact record at creation time. Closed-won and closed-lost reasons from m-savvy custom fields map to GoHighLevel Opportunity custom fields.

M-savvy pipeline definitions and custom stage names read from the API schema map to GoHighLevel Pipeline and Stage configuration. We create GoHighLevel pipelines matching the m-savvy structure before Opportunity import begins. Stage probability percentages transfer from m-savvy to GoHighLevel stage probability settings. If stage count exceeds GoHighLevel's practical limit (typically 15 stages per pipeline), we discuss consolidation options during scoping.

M-savvy separates Leads from Contacts in its data model. GoHighLevel does not have a separate Lead object; all prospects live as Contacts. We apply a split rule during migration: Leads with a qualified status property migrate as GoHighLevel Contacts in an early pipeline stage, and Leads without qualification data migrate as GoHighLevel Contacts with a lead source tag. The original lead status is preserved in a custom field for segmentation.

M-savvy activity records (emails, calls, meetings, tasks) linked to Contacts or Deals migrate to GoHighLevel Activity Log entries. We preserve the activity type, timestamp, owner, and content body. Each activity is linked to its parent Contact by email or GoHighLevel Contact ID resolution. Deleted or archived activities in m-savvy are excluded. Activity associations with attachment files are flagged if the parent record fails migration.

M-savvy custom objects discovered via API inspection (no public schema reference exists) migrate to GoHighLevel custom fields on the relevant standard object. We inspect the live m-savvy API during discovery to enumerate all custom object types, their fields, and relationships before migration. Custom object relationships to Contacts or Accounts map to GoHighLevel Contact or Opportunity custom fields. Any custom object without a clear parent relationship is flagged for the customer to decide whether to flatten into an existing object or treat as a separate data set.

M-savvy stores attachment files separately from record data and requires a dedicated file-export pass using m-savvy file API endpoints. We download all attachments to our staging environment, upload them to GoHighLevel Media Library, and relink each file to its parent record by ID post-ingestion. If a parent record fails to migrate, its attachments are held in a quarantine queue for manual review. File metadata (filename, type, size) is preserved in a custom field on the linked Contact or Opportunity.