Migrate your Fieldmagic data

Primary billing entity in Fieldmagic. Customers relate to Sites and Contacts. We migrate Customers as-is with standard fields and preserve their relationship IDs to Sites and Contacts using Fieldmagic's native import wizard field-ordering format.

Physical service locations linked to a Customer. Each Site can have multiple Assets. We preserve the Customer-Site relationship by mapping Customer IDs or external references at import time. Sites are a mandatory hub object in the data model.

Individual people linked to a Customer (not directly to a Site). Contacts can be associated with multiple Sites under the same Customer. We migrate Contacts with their Customer link preserved and flag any Contacts without a Customer parent for manual assignment.

Categories that define the class of equipment being tracked (e.g., 'HVAC Unit', 'Boiler'). These are reference data objects with no external dependencies. We migrate Asset Types directly and re-link them to Assets after migration.

Individual equipment records linked to a Site and an Asset Type. The Site-Asset relationship must be preserved by referencing the correct Site external ID at import time. Assets also carry maintenance history which we flag for sequencing after the core record is created.

Core workflow object representing a field service job. Jobs link to a Customer, Site, Asset, and one or more Schedules. We migrate Jobs with all linking fields preserved and sequence Schedules after Jobs are loaded. Jobs have status fields that require value mapping if the destination uses different status labels.

Sales quotations that can be converted to Jobs. Quotes link to Customers and Sites. We migrate Quotes as standalone records and flag any that are in a 'converted' state for relationship reconciliation against the target system's corresponding Jobs.

Sub-objects within a Job representing individual work steps. Tasks link to a Job and can be assigned to a technician. We preserve Job-Task parent relationships. Tasks auto-mark as 'Unscheduled' when all associated Schedules are removed (Fieldmagic behavior, confirmed in release notes March 2025).

Time allocations linking a Job or Task to a technician and time slot. Schedules are independent records that reference Job and User IDs. We migrate Schedules after Jobs and Users are in place, preserving the Job-Schedule and User-Schedule links.

Billing records generated from Jobs. Fieldmagic supports fixed-price and time-and-materials invoicing. Invoices reference a Customer and Job. Open vs. paid status must be mapped to the destination's invoicing workflow. Historical paid invoices are migrated as read-only records.

Inspection or compliance checklists that can be auto-attached to Jobs or Quotes at creation (confirmed March–April 2025 release notes). Checklists and their completed responses must be linked to the correct Job ID. We handle checklist attachments separately from the core Job record to preserve completion data.

Recurring service agreements that define contract pricing used during Job billing. Contracts link to Customers and drive invoicing behavior. Contract-to-Job relationships require value mapping at the line-item level, as contract pricing rules are destination-specific.

Office users and mobile technicians. An office license includes mobile app access. We migrate Users with their role and license type preserved. Technician scheduling assignments require User IDs to be in place before Schedules are loaded.