Migration & data
Workiz Data Export for Migration: What to Request and Verify
Request an entity-by-entity export and verify the files actually supplied. A customer marketing-list connection is not evidence that jobs, invoices, payment allocations, and attachments have been preserved for a plumbing software migration.
In this guide
Do not confuse a contact sync with an operational backup
Workiz documents a Mailchimp client-list sync, including conditions on which contacts are sent. That is a marketing-list workflow, not documentation of a complete export of linked operational and financial records. Official source
This guide therefore does not invent a Workiz export menu or promise a particular plan entitlement. Confirm the current export options with the vendor and inspect the resulting files before planning cutover.
Send a specific export request
We are preparing a controlled migration of our plumbing business data.
Please confirm the currently supported export options for:
- customers, contacts and service properties;
- estimates/quotes and relevant statuses;
- jobs, assignments and open-work status;
- invoices, line items and remaining balances;
- payment transactions, refunds and invoice allocations;
- service/pricebook items;
- important notes and attachments.
For each dataset, please identify the format, available identifiers,
relationship fields, relevant permissions, limitations and any
separate archive process. Please also explain how export filters and
account-access changes affect the available records.
Ask for clarification when a response says only “all data.” A list of entities and fields is more useful than an undefined completeness claim.
Inspect the supplied files before cleaning them
Save original copies and record the source, export date, and scope. Check whether identifiers, line items, and relationships are present rather than assuming that a row with a customer name contains the full history.
Keep unknown or unsupported fields in a mapping register. Do not silently drop an internal note, property relationship, or payment reference because the destination has no obvious column with the same name.
Distinguish financial concepts
A paid label, a zero remaining balance, and a payment transaction are different pieces of information. The migration should preserve their meaning rather than making a financial conclusion from a single status field.
For example, a fictional invoice can reach zero balance through a payment, a credit adjustment, or another approved resolution. Only the actual source evidence tells you which occurred.
Use the accountant's review for classifications and reconciliation. Do not create invented payments to make imported balances look complete.
Test a representative sample
| Sample case | What to verify |
|---|---|
| Repeat customer | Jobs remain linked to the right identity |
| Multiple properties | Service address and unit remain distinct |
| Open job | Next action and status are preserved |
| Partial payment | Charge, payment and remaining balance agree |
| Attachment | File remains accessible through a documented reference |
| Rejected field | Information is preserved or explicitly flagged |
The destination's current import support determines what can become a native record. This article does not assert full Workiz-to-GoPlumber compatibility without that testing.
Cut over only with an exception list
Reconcile source and destination counts, active jobs, and financial controls. Record any gaps, their operational impact, and the chosen preservation or resolution method.
Keep appropriate old-system access or verified archives until the business can continue its work and explain its records. A successful contact import is useful, but it is not a complete migration sign-off.
Sources and editorial notes
Product and documentation references checked September 29, 2026. GoPlumber publishes this guide about its own product category. Examples and templates are original illustrative material, not customer case studies or market benchmarks. Confirm current vendor terms before acting.