A safer FieldPulse import workflow
Moving from FieldPulse should not force your office to rebuild every customer relationship from memory. Contacts, locations, jobs, estimates, invoices, and the links between them are operating context—not archive material.
Local Business Pro now includes a first-class FieldPulse import workflow for supported multi-file migrations. It analyzes the source package as a connected set, keeps source identity visible, and lets the team review what can be established before it relies on the result.
Review the source package together
A contact can depend on a location. A job needs the right customer context. An invoice is more useful when its history remains understandable. The FieldPulse workflow is designed around those relationships rather than treating every uploaded file as a separate, unrelated spreadsheet.
That does not mean every custom field, undocumented export variation, or ambiguous historical relationship can be recreated automatically. When the source does not establish an answer, the right product behavior is to surface a decision—not invent a record.
Dry-run before a live migration
The team can dry-run the supported import before records are created. That is the moment to inspect the plan, resolve a source question, or stop if the result does not match the business’s expectation.
An authorized live import runs through a queued workflow with status and history. The office can return to review what was created, skipped, or needs attention instead of relying on one browser tab to tell the whole story.
The Import & Export workspace explains the broader operating pattern. For other source systems, see the Housecall Pro controlled migration path and relationship-aware Jobber update.
What to verify before and after a migration run
Before a run, keep the source package intact, identify the records your office needs to recognize first, and decide who can resolve exceptions. After a dry run or authorized import, compare the result against the source: check that expected contacts and locations are recognizable, that key jobs, estimates, invoices, and catalog records are accounted for where supported, and that skipped or reviewable outcomes have an owner. This workflow is about making migration evidence inspectable, not declaring every historical export perfect.
Frequently asked questions
Can I review the FieldPulse import before it creates records?
Yes. The supported workflow includes a dry run so the team can inspect the proposed outcome before an authorized live run.
Does it preserve every FieldPulse field and relationship?
No. It carries the supported records and relationships that the source evidence can establish. Missing or unclear information remains visible for review.
What happens after an interrupted run?
Use the queued-run status and history to understand the prior outcome, correct the source or decision if needed, and take the supported recovery step.
