Migrate from MobiWork to HighLevel

MobiWork customers map to HighLevel contacts. Customer name, phone, email, address, and company association transfer directly. MobiWork's customer type (commercial vs residential) is preserved as a custom pick-list field on the HighLevel contact. During migration, any associated notes or tags are also transferred as custom text fields, ensuring no customer context is lost.

MobiWork prospects without a closed-won status migrate as HighLevel contacts with a 'Lead' tag. Any prospect notes or estimated job value carry over as custom fields on the contact record. The original prospect creation date is preserved as a custom date field for pipeline timing analysis.

MobiWork's company records (used for B2B customers) map to HighLevel's Company object. Company name, address, industry, and employee count transfer directly. Primary contact association resolves via email match after contact migration. If multiple contacts share the same company name, the system links the first matching contact and flags duplicates for review.

Work orders have no native HighLevel equivalent — HighLevel has Tasks but not structured work-order records. We create a Work_Order__c custom object in HighLevel with fields for job type, status, scheduled date, assigned technician, and location. Work order line items map to a related custom object.

MobiWork quotes become HighLevel opportunities. The opportunity name derives from the quote title, the estimated amount maps to the opportunity value, and the quote status (Draft, Sent, Accepted, Declined) maps to HighLevel pipeline stage values. Line items require manual rebuild in HighLevel's product catalog.

MobiWork invoices migrate to a custom Invoice__c object linked to the contact and opportunity. Invoice number, total amount, balance due, and payment status map as custom fields. Payment transaction history requires a separate custom object for multi-payment invoices. Each invoice also records its original MobiWork ID for reconciliation.

MobiWork's dispatch board and schedule records have no HighLevel equivalent. We preserve schedule date, assigned technician, and job location as custom date and text fields on the Work_Order__c record. Appointment slots map to HighLevel Calendar events manually after migration. Your team should review the mapped fields for accuracy before creating calendar events.

MobiWork employees and technicians map to HighLevel users by email match. Active/inactive status, role, and phone number carry over. MobiWork's user-specific routing preferences are stored as custom text fields on the HighLevel user record. If an employee email does not match an existing HighLevel user, a new user account is created and flagged for activation.

MobiWork inventory and parts catalog migrates to a custom Inventory_Item__c object. SKU, name, description, unit cost, and quantity-on-hand map as custom fields. Part usage on work orders links via relationship fields. All inventory records retain their original MobiWork part ID to facilitate reconciliation after migration.

MobiWork file attachments (photos, signatures, PDFs) on work orders and invoices download and re-upload to HighLevel Files. Files attach to the corresponding contact, Work_Order__c, or Invoice__c record. File size limits follow HighLevel's upload constraints. We also verify that each file is correctly linked and accessible within the respective record's media gallery.

MobiWork custom properties on customers, work orders, and invoices map to HighLevel custom fields on the corresponding object. Field type mapping: text to Short Text, number to Number, date to Date Picker, dropdown to Dropdown. Custom fields must be pre-created in HighLevel before migration.

MobiWork payment transactions (Stripe, Clearent) migrate to a custom Payment__c object linked to the Invoice__c record. Payment date, amount, method, and transaction ID map as custom fields. Partial payments aggregate on the invoice record. Each payment record retains its original MobiWork payment reference for audit trails.