Migrate from ServiceMax to HighLevel

ServiceMax Work Orders map to HighLevel Opportunities, which represent service jobs in a Pipeline. Work order fields (status, priority, type, location) become custom fields on the Opportunity. The original Work Order number is stored for traceability. Multi-line items (tasks, parts used) may require a custom object if detailed line-item reporting is needed in HighLevel.

When work orders have complex nested data — multiple technician assignments, detailed parts consumption logs, or signature capture — we create a HighLevel custom object to capture this structure. Each ServiceMax Work Order line item becomes a custom object record associated to the parent Opportunity. HighLevel allows up to 10 custom objects per sub-account, so we plan object allocation upfront.

ServiceMax Assets represent customer equipment under service. These map to HighLevel Company records with custom fields capturing asset name, serial number, product family, installation date, warranty status, and location. Multiple assets associated to one customer map to one Company record with multiple custom object records for individual asset detail.

Standard Contact fields (first name, last name, email, phone) map directly to HighLevel Contact fields. ServiceMax contact roles on Work Orders (Dispatcher, Technician, Customer Contact) become custom fields or tags on the HighLevel Contact record. Primary contact resolution is based on email address matching against HighLevel users.

ServiceMax technicians are mapped by email to HighLevel users. Skills, certifications, and service territories from ServiceMax become custom fields on the HighLevel User record. Unmatched technicians are flagged and assigned to a fallback user or migrated as Contact records with a 'Technician' tag.

ServiceMax service contracts (entitlements, maintenance agreements) have no direct HighLevel equivalent. We create a Service Contract custom object with fields for contract type, start/end dates, covered products (linked to Asset custom objects), and SLA terms. Contract status (Active, Expired, Cancelled) maps to a pick-list field on the custom object.

ServiceMax product catalog (products, parts, tools) maps to a HighLevel custom object. Product name, SKU, product family, and description become custom fields. Parts BOM (Bill of Materials) relationships from ServiceMax may require junction custom objects in HighLevel if multi-level product structures are needed for quoting.

ServiceMax task records (service visits, phone calls, follow-ups) map directly to HighLevel Tasks. Original timestamps, assigned users, and parent record links (Work Order or Contact) are preserved. HighLevel Tasks appear in the contact timeline and can trigger workflow automations. These tasks can also be associated with custom objects for detailed service tracking.

ServiceMax cases (customer issues, complaints) map to HighLevel Tasks with a 'Case' tag, or to a custom object if detailed case tracking (resolution codes, case type, priority) is required. We recommend a custom object for organizations with high case volume that need reporting separate from pipeline opportunities.

ServiceMax service locations map to HighLevel Company address fields. Multiple service locations per customer become multiple Company records or Address custom object records linked to a single parent Company. GPS coordinates from ServiceMax are stored as custom decimal fields for reference.

Work order line items (parts used, labor hours, travel charges) map to a custom object in HighLevel. Each line item record links to the parent Opportunity (Work Order) and includes quantity, unit price, line type, and product reference. This preserves detailed billing and parts consumption history from ServiceMax.

ServiceMax technical attributes (equipment specifications, configuration data) become custom fields on the Asset custom object in HighLevel. ServiceMax's attribute template structure is mapped to individual custom fields per attribute group. HighLevel's custom field type support (text, number, pick-list, date) accommodates most attribute types.

Files attached to ServiceMax records (photos, PDFs, signatures, documents) are downloaded and re-uploaded to the corresponding HighLevel record (Opportunity or custom object). HighLevel's 25MB per-file limit applies. Large files are flagged before migration. Inline images in notes are extracted and hosted separately.

ServiceMax preventive maintenance schedules map to a custom object tracking frequency, interval, last completed date, and next due date. PM task generation logic does not migrate — HighLevel workflows can be configured to create Tasks on schedule, but the PM plan rules must be translated into HighLevel workflow triggers manually.

ServiceMax inventory locations (warehouses, technician vans, depots) map to a custom object. Bin locations, stock levels, and reorder points from ServiceMax become custom fields. Real-time inventory sync requires a rebuild using HighLevel's API or a third-party integration — the historical inventory snapshot migrates as data.