Migrate from Sunbase Data to HighLevel

Sunbase Leads capture unqualified prospects from door-to-door sales forms, web capture, and manual entry. We map Sunbase Lead records to GoHighLevel Contact records with the lead_source field set to the Sunbase lead source value. Lead status and assignment data migrate as custom fields on the Contact record. Leads tied to Sunbase automation workflows are documented separately; the automation logic is not migratable and requires rebuild in GoHighLevel's workflow builder.

Sunbase Contact records include standard fields (name, email, phone, address) plus industry-specific fields depending on CRM module configuration. We map each Contact to GoHighLevel Contact, preserving the full name, email, phone, and address fields. Any Sunbase custom fields require a manifest from the customer during scoping because Sunbase does not export field definition metadata. GoHighLevel's custom fields accommodate most Sunbase contact extensions.

Sunbase Deals track the sales cycle including proposals, quotes, and pipeline stages. We map Deals to GoHighLevel Opportunities with the deal value, stage name, and associated contacts. Sunbase's pipeline stage names migrate as GoHighLevel pipeline stage values. Custom deal fields require explicit mapping during scoping. The deal's associated Contact links via GoHighLevel's Contact-Opportunity relationship.

Sunbase pipeline configurations (stage names, board positions) migrate as data values in GoHighLevel. We create a GoHighLevel custom pipeline before migration and populate stage names to match Sunbase's board. The visual drag-and-drop layout cannot be reproduced programmatically; we document the original layout for the customer's admin to reconfigure manually in GoHighLevel's pipeline editor.

Sunbase Projects represent installation or job-site operations with metadata, status, budget tracking, and linked work orders. GoHighLevel does not have a native project record type. We migrate Projects as GoHighLevel Custom Objects (available on Starter $97/mo and above) with fields for project name, status, budget, and an external_project_id reference back to the Sunbase record. If the customer's GoHighLevel tier does not support Custom Objects, we create a tagged note attached to the associated Contact or Opportunity with project details.

Sunbase Work Orders include permit info, task details, attachments, and system specifications. We map Work Orders to GoHighLevel Custom Objects with fields for permit info, task details, and system specifications. Linked employee assignments and scheduling data map to GoHighLevel Tasks or Appointments. Attachments migrate as GoHighLevel documents attached to the Custom Object or parent Contact record.

Sunbase Invoices include line items, payment status, and linkage to the originating project or client. We map Invoices to GoHighLevel Custom Objects with invoice number, line items, total amount, payment status, and a linked Contact. Historical paid invoices migrate with their full detail. If GoHighLevel Payments is enabled on the destination account, we link Invoice records to GoHighLevel Payment records where applicable.

Sunbase Client records represent contracted customers distinct from Leads and Contacts. We map Client records to GoHighLevel Contact records (for individual clients) or create a GoHighLevel Contact with a company flag for business clients. The mapping choice depends on whether the customer uses GoHighLevel's account model or manages all relationships at the Contact level.

Sunbase Employee records include HR data, crew assignments, and role metadata. We map Sunbase Employees to GoHighLevel Users for team members who need CRM access. GPS location history and crew assignment data migrate as custom fields on the User record or as linked Custom Object records. External-only employees (no CRM login needed) migrate as Contacts with an employee_flag custom field.

Sunbase Appointments include customer-linked scheduling, date, time, assigned contact, and status. We map Appointments to GoHighLevel Appointments with the calendar date, time, assigned Contact, and status preserved. Sunbase's Google Calendar sync linkage is not transferable; appointments migrate as new GoHighLevel calendar entries. Any appointment notes or details map to the GoHighLevel Appointment description field.

Sunbase Documents include contracts, financing applications, and permits stored within the platform. We extract binary files and preserve file names, upload dates, and associations to the parent record (Contact, Deal, Project). Documents attach to the mapped GoHighLevel record (Contact, Opportunity, or Custom Object) via GoHighLevel's file attachment mechanism. Large file attachments may require additional scoping if storage limits on the destination GoHighLevel plan are constrained.