Migrate from Successware to HighLevel

Successware customer records (name, phone, email, address) map directly to HighLevel contacts. HighLevel's flat contact model accommodates Successware's customer type distinctions (residential vs. commercial) via a custom pick-list field. Multiple service addresses per customer collapse to one primary contact address; additional locations stored as contact custom fields.

Successware business-name customers map to HighLevel company records. Company-level fields (business name, industry, number of employees) map to HighLevel company fields. Successware's commercial-vs-residential flag becomes a custom field on the company record. Parent-company relationships in Successware map to HighLevel company associations.

Successware jobs are the core service record — they contain customer link, technician, line items, status, and history. HighLevel has no native job or service-ticket object, so jobs migrate as Opportunities with a custom Job_ID__c field linking back to the Successware record. Pipeline stages are created to mirror Successware job statuses (Scheduled, In Progress, Completed, Invoiced, On Hold). Job totals map to opportunity monetary values where applicable.

Successware job statuses (Open, Scheduled, Dispatched, Completed, Invoiced, Closed) are mapped value-by-value to HighLevel pipeline stages. Each Successware status gets a corresponding stage in the HighLevel pipeline so reporting continuity is preserved. Stage-entered timestamps are stored as custom datetime fields since HighLevel's stage history is not a native object.

Successware employee records (name, email, phone, role, skills) map to HighLevel users. Email matching is used to link Successware technician assignments to HighLevel user accounts. Users without email matches are flagged before migration; you either create HighLevel accounts first or assign their records to a fallback user. Roles and skills migrate as custom fields on the user record.

Successware invoices have no direct HighLevel equivalent. Invoice header data (invoice number, date, total, balance due, payment status) migrates as custom fields on the linked opportunity. Line items migrate as a custom text field or JSON-encoded custom field. Paid invoices retain their paid status as a custom pick-list value. Full accounting (A/P, cost tracking, general ledger) does not migrate — rebuild with QuickBooks, Xero, or a dedicated accounting tool.

Successware PriceBook items (description, unit cost, labor rate, part number) have no native HighLevel equivalent. These migrate as a custom PriceBook object in HighLevel with custom fields for each attribute. Each PriceBook item can then be linked to opportunities via a lookup relationship. Custom object creation in HighLevel requires API or UI setup per sub-account.

Successware job history (status changes, technician notes, dispatch events) has no HighLevel native equivalent. We migrate job history as a custom Job_History__c long-text field on the opportunity record and append key history events as HighLevel notes linked to the opportunity. Original timestamps and technician names are preserved in the custom field value.

Successware prospects that have not yet converted to jobs map to HighLevel contacts without an associated opportunity. Prospect source (referral, marketing campaign, walk-in) migrates as a custom Contact_Source__c field. HighLevel tags are applied based on the original Successware prospect category.

Successware's A/R aging report is a financial view, not a transactional record. Outstanding invoice amounts and aging buckets migrate as fields on the associated opportunity record (Outstanding_Balance__c, Aging_Bucket__c). The full aging report is exported as a CSV and stored as a HighLevel attachment for reference. Reconciliation against HighLevel's opportunity amounts is done post-migration.

Successware custom fields on customer records (e.g., preferred contact method, property type, credit limit) migrate to HighLevel custom fields on the contact record. Each custom field in Successware is evaluated for type (text, number, pick-list) and recreated in HighLevel. Pick-list values require explicit value-by-value mapping.

Successware file attachments on jobs and customers re-upload to HighLevel as Files linked to the corresponding contact or opportunity record. File size limits in HighLevel apply (attachments over 25MB split or linked externally). Original file names and upload timestamps are preserved in the HighLevel file metadata.