Migrate your mQuest data

Work Orders are the core FSM object in mQuest. We map Work Order fields including status, priority, scheduled date, assigned technician, site location, and line items. Custom fields on Work Orders require field-level mapping during migration.

Jobs are the parent record for service activity. We migrate Jobs with their full lifecycle states, linked Customer records, site addresses, and job-type classification. Job status transitions are preserved as state-change history in the target system.

Technician records include name, certification tags, scheduling availability, and territory assignment. We map these fields and flag any technician-specific custom properties that require explicit field mapping at migration time.

Customer records in mQuest include billing and service addresses, contact details, and service-level agreement terms. We migrate Customer records with their full address hierarchy intact.

Assets represent equipment linked to a Customer or Location and are associated with Jobs. We map the asset-to-job linkage but note that custom asset fields require field-level review during scoping.

Service Sites define physical locations tied to a Customer account. Address normalization is applied during migration to ensure consistency with the destination system's location schema.

Invoiced amounts and payment status linked to completed Jobs can be migrated. We flag that open invoice reconciliation requires explicit confirmation of fiscal period alignment between source and destination.

mQuest supports custom fields on Work Orders, Jobs, and Assets. Custom field schemas vary by tenant. We inspect the field catalog during discovery and map each custom field explicitly rather than assuming a standard schema.