Migrate from ServiceTracker to HighLevel

ServiceTracker stores customer records as Account-equivalent entities with contact details attached. FlitStack splits these into HighLevel Company records (for business name, address, industry) and Contact records (for individual name, phone, email, role). The primary contact per customer becomes the primary Contact linked to the Company via the CompanyId field.

ServiceTracker work orders map directly to HighLevel Opportunities. The work order name becomes the Opportunity name, the quoted or invoiced amount maps to Opportunity Amount, and the work order status (Open, In Progress, Completed, Cancelled) maps to a Pipeline Stage pick-list value. Additional job details (service type, technician, site) migrate as custom fields on the Opportunity.

ServiceTracker work order status values are mapped one-by-one to HighLevel Pipeline stage names. Teams with multiple work order categories (e.g., Inspection, Treatment, Emergency) each require their own HighLevel Pipeline with stage values scoped to that pipeline. The migration plan defines the value map before records are loaded.

ServiceTracker sites store the physical service address, access notes, GPS coordinates, and site-specific instructions. HighLevel has no dedicated site object, so site address and coordinates migrate as custom fields on the related Contact or Company record (Site_Address__c, Site_Latitude__c, Site_Longitude__c). Multiple sites per customer collapse to the primary site in the primary Contact record; secondary sites surface as additional address custom fields.

ServiceTracker asset records track serial numbers, model numbers, install dates, warranty expiration, and maintenance history per piece of equipment. HighLevel has no native asset object, so FlitStack creates an Equipment__c custom object with fields for Serial_Number__c, Model__c, Install_Date__c, Warranty_Expiry__c, and a ContactId or CompanyId lookup to link equipment to the customer record. Asset maintenance history migrates as custom note fields or linked child records.

ServiceTracker technicians are staff records with name, phone, certifications, and territory. HighLevel users are created by email invitation; FlitStack resolves each technician's email against HighLevel users and maps the OwnerId on migrated Opportunities. Unresolved technicians are flagged before migration — your team either invites them to HighLevel or assigns their records to a fallback user.

ServiceTracker tracks parts and inventory consumed per work order. For migrations with infrequent or simple inventory usage, parts lists migrate as a multi-line text custom field on the Opportunity. For high-volume or multi-part jobs, FlitStack creates a Job_Parts__c custom object linked to the parent Opportunity so each part has its own record with quantity, SKU, and description.

ServiceTracker invoice records (amount, date, status, payment method) have no native equivalent in HighLevel's CRM model. FlitStack creates an Invoice_Reference__c custom object or migrates invoice data as read-only custom fields on the Opportunity for audit continuity. Actual billing and payment processing must run through a QuickBooks or Stripe integration post-migration.

ServiceTracker compliance records (regulatory checkboxes, inspection results, hazard notes) attach to work orders for pest control and environmental service teams. These migrate as custom Yes/No or text fields on the Opportunity record. FlitStack surfaces the full compliance checklist as a structured set of custom fields so field techs can reference requirements in HighLevel's mobile view.

ServiceTracker file attachments on work orders (photos, PDF reports, signed forms) are downloaded and re-uploaded to HighLevel Files, linked to the corresponding Opportunity record. HighLevel file size limits (25MB per file) apply. Inline images in compliance notes are extracted and rehosted individually.

ServiceTracker allows custom fields, formula fields, and pick-list menus created without code. Each custom property in ServiceTracker maps to a corresponding custom field in HighLevel on the appropriate object (Contact, Company, Opportunity, or Custom Object). Pick-list values are mapped value-by-value; formula field results are computed and stored as static values at migration time.