Migration & data
FieldPulse Migration Checklist for Plumbing Business Records
Before switching from FieldPulse, confirm the export options available to your account and inventory every record type you need. Preserve source identifiers and test real relationships instead of assuming that a generic spreadsheet import covers the entire business history.
In this guide
Confirm capabilities rather than guessing the interface
This checklist does not assert a particular FieldPulse export button, file format, or plan entitlement. Verify those details in the current account and with the vendor before committing to a migration schedule. Official source
FieldPulse publishes a pricebook product page, but the existence of that feature does not establish how every item, historical price, or relationship can be exported. Treat product capability and data portability as separate questions.
Inventory the records that support daily work
FieldPulse migration checklist
[ ] Customer identities and contact roles
[ ] Service properties and unit relationships
[ ] Open estimates and selected versions
[ ] Scheduled, unfinished and completed jobs
[ ] Invoices, line items and balances
[ ] Payment transactions and allocations
[ ] Refund or credit history where relevant
[ ] Pricebook/service items and scope descriptions
[ ] Notes, photos and other attachments
[ ] Current permissions and access arrangements
[ ] Export limitations and unavailable fields documented
Decide which records must be usable in the new operational system and which may be preserved in a readable archive. Do not make that choice silently after discovering an import limitation.
Ask for the relationship fields
A customer export without property or job references may preserve names but lose the business history. Ask which identifiers connect the separate datasets.
Retain source-system IDs in the working files wherever available. Do not use a person's name or a dollar amount as the sole basis for joining records.
For pricebook items, distinguish cost, selling price, unit, customer description, and internal notes. A field with a familiar label can still have a different meaning in the destination.
Prepare a small test package
Choose a customer with more than one relevant record, an open job, a completed job, and a financial example requiring careful review. Include a long description and an attachment reference where those are part of your history.
Keep original exports unchanged. Clean working copies and record each transformation, including any split or combined fields.
Do not assume that GoPlumber accepts every FieldPulse entity or column. Check the current import path and preserve anything unsupported through an explicit process.
Reconcile outcomes, not just upload counts
| Control | Question |
|---|---|
| Record counts | Are all included source rows accounted for? |
| Relationships | Does the job belong to the correct customer and property? |
| Status meaning | Has the source meaning been preserved? |
| Financial values | Are charges, payments and balances distinguished? |
| Attachments | Can the business retrieve the necessary files? |
| Exceptions | Is every missing or ambiguous field visible? |
An import can finish successfully while still producing the wrong customer relationships. Inspect the actual records and documents.
Plan the final cutover
Record the export cutoff and how new work entered afterward will be captured. Verify contractual and data-access arrangements before reducing or ending access to the old system.
A sound migration decision is based on what was actually exported, mapped, tested, and preserved. The checklist helps make those decisions explicit without promising a level of portability that has not been verified.
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.