Migrate from Service Toolz to HighLevel

Service Toolz contacts map directly to HighLevel contacts. We map first name, last name, email, phone, address, and all custom contact properties. Owner resolution uses email match against HighLevel users. Duplicate contacts detected by email are flagged before migration. If the same contact appears in multiple Service Toolz records, we merge them into a single HighLevel contact and retain references to all linked work orders, quotes, and appointments.

Service Toolz company records map to HighLevel companies. Company name, domain/website, address, industry, and employee count transfer as direct field mappings. Parent-company hierarchies in Service Toolz map to HighLevel company relationships. During discovery we verify whether any companies share the same name in Service Toolz to prevent duplicate company records from being created during migration.

Service Toolz quotes have line items, amounts, and status (Draft, Sent, Accepted, Declined). We map accepted quotes to HighLevel Opportunities with amount preserved and status mapped to a pipeline stage. Pending quotes can become Opportunities in a 'Quote Pending' stage or remain as a Custom Object depending on your reporting needs.

Service Toolz work orders have no native equivalent in HighLevel. We map work orders to a 'Work Order' Custom Object with fields for work order number, description, assigned technician, status, scheduled date, and linked contact/company. The Custom Object must be pre-created in HighLevel before migration — we deliver the schema plan.

Service Toolz inventory items with stock levels, SKUs, and reorder points split into HighLevel Products (for catalog/sales use) and a 'Inventory' Custom Object (for stock tracking). If you only use products for quotes, HighLevel Products alone may suffice — we determine this during discovery.

Service Toolz technicians are staff records, not contacts. We resolve them by email against HighLevel users — matched technicians become HighLevel users/team members. Unmatched technicians are flagged so you can create their HighLevel accounts before migration or assign their records to a fallback user.

Service Toolz scheduled appointments map to HighLevel appointments, preserving the appointment type, start and end datetime, linked contact, assigned technician resolved to a HighLevel user, and any notes attached to the appointment. Appointment types in Service Toolz must be pre-created in HighLevel's Calendars section under Settings > Calendars > Appointment Types before migration runs to ensure the appointment type field maps correctly.

Service Toolz invoices with payment status map to HighLevel Opportunities with a Stripe payment link field or a linked Custom Object for invoice metadata. Paid invoices map to Closed Won opportunities; unpaid invoices retain their status. HighLevel's built-in Stripe integration handles payment processing post-migration.

Service Toolz task checklists attached to work orders migrate as HighLevel Tasks linked to the work order Custom Object. Standalone tasks migrate as HighLevel Tasks under the associated contact or opportunity. Original create dates and assignees (resolved by email) are preserved.

Service Toolz tags and labels map directly to HighLevel tags without any transformation. Tags on contacts, companies, and opportunities transfer as HighLevel contact/company/opportunity tags respectively. Tag-based segmentation in Service Toolz maps to HighLevel Smart Lists and workflow triggers after migration, enabling you to recreate automated actions based on the same tagging logic.

All Service Toolz custom contact, company, and work-order properties migrate to HighLevel custom fields on the corresponding object, or to custom object fields if the destination object is a Custom Object. We create fields in HighLevel before migration and deliver a field-creation checklist.