Migrate from MobiWork to HubSpot

MobiWork stores both personal and business information on one customer record. FlitStack AI splits these: personal name, email, phone, and home address become HubSpot contact properties. Company name, business address, and industry become HubSpot company properties. A custom property flags the original MobiWork customer type so your team can verify the split.

MobiWork customers can carry multiple service addresses. The primary address maps to the HubSpot company address. Secondary service locations create additional address properties on the company record or associate as related contacts with location-specific properties. Each location retains its own street, city, state, and zip code for accurate service dispatch and reporting.

MobiWork quotes carry line items, pricing, and status. FlitStack AI maps them to HubSpot deals, preserving the quoted amount as the deal amount, quote status as a custom deal property, and line items as deal products. The original MobiWork quote number is stored in a custom field for traceability.

MobiWork work orders have no direct equivalent in HubSpot — they are job tickets with technician assignment, status, priority, description, and time entries. FlitStack AI maps these to HubSpot tickets and preserves technician assignment as a contact lookup or owner property, work order status as a custom pick-list property, and priority as a custom field matching your HubSpot ticket SLA tiers.

MobiWork work order statuses (New, Scheduled, In Progress, On Hold, Completed, Cancelled) map to HubSpot ticket pipeline stages. Each MobiWork status value maps to a corresponding HubSpot ticket stage value by value. Your HubSpot admin defines the ticket pipeline before migration.

MobiWork recurrent services link a customer to a contract with billing frequency. FlitStack AI maps these to HubSpot deals with a custom contract-type property, associated to the primary contact and company. Recurring invoice history is preserved as line items on the deal.

MobiWork invoices carry line items, tax, and payment status. FlitStack AI migrates invoice data as deal products on the associated HubSpot deal. Payment status (Paid, Pending, Overdue) becomes a custom deal property. Full invoice PDFs are re-uploaded to the deal's file attachments.

MobiWork time tracking entries record technician hours per work order. FlitStack AI aggregates time entries per work order and stores total hours as a numeric custom property on the corresponding HubSpot ticket. Individual time entry timestamps are preserved in a custom text property if your team needs granular audit data.

MobiWork inventory items (parts catalog, stock levels, cost per unit) migrate to HubSpot products with custom fields for stock quantity, unit cost, and vendor. If your team used parts primarily for job costing rather than inventory management, the data may fit better as custom properties on tickets.

MobiWork crews group multiple technicians for a job. FlitStack AI maps crew names to HubSpot custom properties on tickets. Individual technician assignments map to the ticket owner or a custom multi-select property. Your HubSpot admin decides whether to model crews as a custom object or as tagged groupings.

MobiWork route optimization data (sequence, travel time, geographic coordinates) has no HubSpot equivalent. FlitStack AI exports route plan JSON and stores raw coordinates as custom latitude/longitude properties on the associated contact records. Your routing logic must be rebuilt in a HubSpot-compatible scheduling tool.

MobiWork electronic forms (signatures, photos, inspection data) stored as attachments on work orders migrate as file attachments on the corresponding HubSpot ticket. Original file names and timestamps are preserved. These attachments are uploaded to HubSpot's file manager and linked to the ticket record, maintaining a complete audit trail for compliance and future reference.

MobiWork custom fields on any object migrate as HubSpot custom properties. All custom properties must be pre-created in HubSpot before the migration runs. FlitStack AI delivers a custom property creation checklist mapped from your MobiWork custom field inventory. This checklist includes property name, data type, pick‑list options, and the target HubSpot object for each field.

MobiWork owner and technician records match to HubSpot users by email address. Unmatched owners are flagged before migration — your team creates the HubSpot user or assigns a fallback owner before the full run. This prevents tickets landing without a valid HubSpot owner.