Migrate from Shark Byte CRM to HighLevel

Shark Byte Customer records (representing the end-client organization or homeowner) map to GoHighLevel Contacts. Standard fields including company name, address, phone, and service history transfer to Contact fields and address custom fields. The Customer record's primary contact point becomes the primary Contact record with the Customer-level data stored in Contact custom fields or linked via the company name for cross-reference. We flag any Customer records without a named contact for admin review before insert.

Shark Byte Contact records (individual points of contact at each Customer site) map directly to GoHighLevel Contacts. Name, phone, email, and role fields transfer to the corresponding GoHighLevel Contact fields. Role classifications from Shark Byte are stored in a Contact custom field since GoHighLevel does not have a native role field on Contact. We use email address as the dedupe key during import.

Shark Byte Estimates are the core product object and contain line items, labor rates, material costs, and contract-term bucket classifications (1-3yr, 3-5yr, 10yr+). We map each Estimate to a GoHighLevel Opportunity with the Estimate total as the Opportunity amount and the term bucket stored as an Opportunity custom field (estimate_term_bucket__c). Line items from the Estimate are stored as Opportunity custom fields or in a custom object linked via lookup relationship. The Estimate's status (draft, sent, approved, expired) maps to the Opportunity stage with a custom stage mapping defined during scoping.

Shark Byte Proposals are generated from Estimates and include pricing, scope, and terms in a generated document. We map Proposal records to GoHighLevel Opportunities and attach the Proposal PDF (extracted from Shark Byte file exports) as a GoHighLevel Contact or Opportunity document. The Proposal's linked Estimate is preserved through the Opportunity custom field estimate_reference__c.

Shark Byte Service Agreements are recurring maintenance contracts tied to specific term buckets. GoHighLevel has no native recurring contract object, so we create a ServiceAgreement__c custom object with fields for contract term (1-3yr, 3-5yr, 10yr+), annual_value__c, start_date__c, end_date__c, and customer lookup to the Contact record. The customer chooses whether to create one ServiceAgreement record per individual contract or aggregate by customer during scoping.

Shark Byte Work Orders track individual jobs dispatched to technicians with status, assigned technician, line items, and attached survey photos. We map Work Orders to GoHighLevel Tasks linked to the relevant Contact and Opportunity. Work Order status (scheduled, in-progress, completed, cancelled) maps to Task status with a custom mapping. Survey photos and attachments are stored as GoHighLevel Contact or Opportunity attachments.

Shark Byte custom fields on Estimates and Service Agreements (equipment specifications, contract classifications, term-dependent pricing logic) map to GoHighLevel Opportunity custom fields or the ServiceAgreement__c custom object fields depending on which object they belong to. GoHighLevel separates Contact custom fields from Opportunity custom fields and once a field type is selected it cannot be switched, so we define the split during scoping before any field is created.

Shark Byte file attachments (scope documents, photos from mobile surveys, signed agreements) on Customer, Estimate, Proposal, and Work Order records are extracted at original resolution where available. Image formats and compression levels vary by the mobile device used in Shark Byte's survey tool. We extract all available files and attach them to the corresponding GoHighLevel Contact or Opportunity record. Some older survey photos may be compressed or missing EXIF metadata.