Migrate your Workiz data

Jobs are the core Workiz object. Every job has a client reference, assigned user, status, scheduled time, and line items. We import jobs as flat CSV/XLS rows and rehydrate client and user relationships on the destination side. Note: if QuickBooks Online is connected to Workiz, importing jobs is not recommended as it can create duplicate payment records — we pause QBO sync during migration.

Clients are the customer records attached to jobs and invoices. Each client has contact info, address, tags, and a history of associated jobs. We map Clients 1:1 to Contacts or the equivalent customer object in the destination CRM.

Leads are distinct from clients in Workiz — they represent unconverted prospects. We migrate Leads into the destination's Lead or Prospect object, preserving source attribution and status. Some destinations do not have a separate Lead object, in which case we merge them into Contacts with a Lead_Status property.

Estimates are attached to jobs and contain line items, pricing, and status. We import estimates as separate objects linked to the parent job. Custom fields on estimates are supported via Workiz's document builder.

Invoices carry line items, payment status, and QuickBooks Online sync metadata. We import open invoices and preserve due amounts and payment history. Paid invoice records are migrated as historical data with payment flags intact. If QBO sync was active, we flag the records to prevent re-sync conflicts.

Items are the product and service catalog entries used in invoices and estimates. We migrate Items into the destination's product or price book. Custom fields on items are preserved as additional properties.

Users are assigned to jobs and carry role-based permissions, GPS tracking settings, and service area assignments. We map Users to the destination's User or Employee object but do not transfer permission configurations — those must be rebuilt on the destination.

Workiz Automations are trigger-action rules tied to job status changes, client conditions, and timing. These are platform-native workflow logic that cannot be exported. We document every active automation so the customer can rebuild them on the destination system.

Workiz supports custom fields on jobs, clients, estimates, invoices, and items. We migrate custom field values as extended properties on the respective objects. Custom field definitions (types, required flags, choice lists) must be recreated on the destination — we provide a field mapping spec to guide this.

Tags are applied to jobs and clients for categorization. We preserve tags as label arrays on the respective records and map them to equivalent tagging or labeling features on the destination.

Workiz tracks real-time GPS coordinates for field techs and stores location history tied to jobs. This is ephemeral operational telemetry that is not exportable via the import tool. We do not migrate GPS history.

Workiz Phone stores call recordings and metadata linked to jobs and clients. These are binary/audio assets not accessible via the import/export layer. Call logs (duration, direction, timestamp) are preserved as activity notes if available in reports.

Service Areas define geographic zones assigned to users and job routing. We migrate the service area boundaries and user assignments as custom geographic fields or linked records on the destination.

Workiz stores payment transactions tied to invoices, including Workiz Pay and third-party gateway records. We import payment status and amounts as invoice sub-records. Actual payment transaction files are not exported.