Migrate from ServeManager to HighLevel

ServeManager Client records map directly to HighLevel Contacts. Full name splits into First Name and Last Name fields. Primary company links via the CompanyId field. Email and phone populate the standard contact fields. Original create date is preserved as a custom field since HighLevel's Created Date is set at migration time.

ServeManager Company records map 1:1 to HighLevel Companies. Name, address, phone, and domain fields migrate directly. Industry and employee-count fields migrate as custom fields since HighLevel Companies have no native equivalent. Parent-company relationships are preserved via the Parent Company ID mapped to a custom lookup field.

Each ServeManager Job becomes a HighLevel Opportunity. Job name and description map to Opportunity name and notes. Amount field migrates to Opportunity monetary fields if the job has a service fee. The serve status (Pending, In Progress, Served, etc.) maps to a custom Status pipeline field in HighLevel, preserving the state progression.

ServeManager's job status pick-list values (e.g., Not Started, Assigned, In Progress, Served, Unsuccessful) map one-to-one to a custom pick-list field in HighLevel. Each status value is recreated in HighLevel's field-builder with the same display label. Status-change timestamps are preserved in a companion custom datetime field.

ServeManager Attempts do not have a native HighLevel equivalent. The most recent Attempt record's details (attempt date, result, server name, GPS) are stored as custom fields on the Opportunity. Historical attempt records are consolidated into a JSON-serialized custom field for reference. If the firm requires per-attempt task records, each Attempt becomes a Task with Type='Service Attempt' linked to the Opportunity.

ServeManager stores latitude and longitude on each Attempt record with a timestamp. HighLevel has no native GPS field. We create a custom text field (Attempt_GPS__c) on the Opportunity and store the coordinates as 'lat,long' strings from the most recent Attempt. Historical attempt coordinates are preserved in the serialized attempt history field.

ServeManager Invoice records map to Opportunity-level custom fields (Invoice_Number__c, Invoice_Amount__c, Invoice_Status__c) and a related custom Payments object. Each invoice becomes a Payment record linked to the Opportunity by a custom lookup field. Partial payments are preserved as line items on the Payment object.

ServeManager job types (e.g., Personal Service, Substituted Service, Publication) migrate both as a custom pick-list field (Job_Type__c) on the Opportunity and as HighLevel Tags applied to the Contact record. The dual mapping preserves the classification for filtering while enabling HighLevel's tag-based workflow triggers.

The assigned process server on a ServeManager Job resolves to a HighLevel user by email match. If the server has an active HighLevel user account, the Opportunity is assigned to them directly. If no match is found, the Opportunity is assigned to a migration fallback user and a custom field (Original_Server__c) preserves the ServeManager server name.

ServeManager's client portal access settings and affidavit template assignments have no HighLevel equivalent. These must be reconfigured post-migration using HighLevel's client portal settings. ServeManager affidavit data (final proof-of-service documents) is exported as file references and re-uploaded to HighLevel's Files feature.

Any custom fields configured in ServeManager for Jobs become custom fields on the HighLevel Opportunity. Field type is inferred from ServeManager's field definition (text, number, date, pick-list) and recreated in HighLevel's field builder with the same label and type before migration runs.

Custom fields on ServeManager Client records (beyond standard name/email/phone) are mapped to custom fields on the HighLevel Contact. Type-aware mapping applies — pick-list values are recreated as pick-lists, numeric fields as numbers, and date fields as dates.