Migrate from BigChange to HighLevel

BigChange persons (customer contacts, operators, technicians) map directly to HighLevel Contacts. Email, phone, and address fields transfer as-is. Operator/technician records that represent staff rather than customers land in HighLevel with a Staff_Role__c custom field to distinguish them from customer contacts.

BigChange company records (customer businesses, site locations) map to HighLevel Companies. Company name, address, phone, and domain fields transfer directly. Multi-site companies in BigChange where each site is a separate company record map to separate HighLevel Company entries with the parent relationship preserved in a Parent_Company__c custom field.

BigChange jobs are the core record type — they contain job type, status, site address, assigned operator, skill requirements, scheduled date/time, and worksheets. These map to HighLevel Opportunities with the job type stored as a custom Opportunity Type field, site address as a custom Site_Address__c field, and operator name as a custom Assigned_Technician__c lookup. Job status maps to pipeline stage via value mapping.

BigChange job statuses (e.g., Booked, In Progress, Completed, Cancelled) map value-by-value to HighLevel pipeline stages. You define the pipeline stages in HighLevel to mirror your BigChange job lifecycle, ensuring the migrated opportunities reflect the same progression. Unmapped statuses are flagged before migration for manual stage assignment.

BigChange quotes (estimates, job-cost documents) contain line items, rates, and custom pricing fields. These merge into the related HighLevel Opportunity as custom monetary fields (Quote_Value__c, Quote_Accepted__c) and a separate Quote Line Items custom object linked to the opportunity. Quote custom fields (quote_custom_fields_v1) transfer as custom fields on the Quote Line Items object.

BigChange invoices, credit notes, and delivery notes have no direct HighLevel equivalent — HighLevel does not have native billing. We create an Invoice custom object in HighLevel with fields for invoice number, amount, status, date, and linked contact/company. Financial line-item detail is stored as a custom related object.

BigChange assets (equipment linked to jobs or sites) have no HighLevel standard equivalent. We create an Asset custom object with fields for asset name, type, serial number, linked company, and linked contact. Asset-job associations are preserved via a custom junction object.

BigChange operator records represent field staff. HighLevel Users are the owner/agent records in the CRM. We attempt email-based matching between BigChange operator emails and HighLevel user emails. Unmatched operators are migrated as a Technician custom object so their assignment history on jobs is preserved even if they are not HighLevel platform users.

Tags applied to BigChange persons, companies, and jobs transfer to HighLevel tags on the corresponding contact, company, or opportunity. Tag names are preserved exactly without modification or reformatting. HighLevel's tag model supports unlimited tags per record, matching BigChange's flexibility.

BigChange custom fields on any object (jobs, quotes, persons, companies) transfer to HighLevel custom fields on the equivalent object. Field data types are mapped: text to text, number to number, date to date, pick-list to pick-list. Long-text fields map to HighLevel's long-text area. Required-field constraints are flagged for admin review before migration since HighLevel enforces them differently than BigChange.

BigChange notes and file attachments linked to jobs, persons, or companies transfer to HighLevel Notes and Files respectively. Original timestamps and creating user are preserved. Files are re-uploaded to HighLevel's file storage. Inline images in rich-text notes are extracted and rehosted.