Contractor Software Migration Checklist

Before switching contractor software, list the records you need, confirm what both systems can transfer, test a small representative sample and check the result against the originals. Decide where new work will be recorded during the move. Keep unresolved records out of a full import until someone has checked them.

For a handyman with repeat customers and small jobs spread across several addresses, a customer list arriving in the new app does not show that the rest of the business is ready to move. Can the office find the correct service address? Can the assigned person read the next visit's notes? Can you still retrieve an old document when a customer asks about it?

Use the checklist below to turn those questions into a test. It is a planning method, not a promise of automatic import, a fixed migration time or compatibility between any two products.

Write down what must keep working

Start with the next real working day, then look backward at the records needed to support it. List active customers, service locations, scheduled work, open estimates and documents that the office must be able to find. Add the details that matter to your business: equipment references, attachments, customer preferences or a second contact for a property.

Separate three decisions:

• Needed for active work: information that must be available in the working system before someone uses it.
• Needed for reference: older material that must remain retrievable through an agreed archive or the existing system.
• Unresolved: anything whose meaning, ownership or transfer method has not been checked.

These are working categories, not a records-retention policy. Do not delete old records because they are outside the active-work list. Get appropriate advice for financial, contractual and retention requirements rather than using a software move to make those decisions accidentally.

Give the checklist an owner. The person preparing an export may not be the person who knows whether a visit, customer balance or job attachment is correct. Record who can answer each kind of question before uploading a file.

Confirm the transfer scope on both sides

Ask the old provider what each export contains and the new provider what each import accepts. A list of available file formats is only part of the answer. You also need the relevant fields, relationships, attachments and status meanings.

For example, Jobber's client-export documentation describes CSV and vCard exports for client information and notes that export availability depends on the plan. That supports a client-list export claim. It is not evidence that the same file transfers your complete job history, payments or attachments into another app.

For each record category, write down:

• The source export or retrieval method and who has permission to use it.
• The destination's supported import or manual-entry method.
• Fields that need mapping, cleanup or separate handling.
• Information that will remain in the old system or a controlled archive.
• Any provider assistance, access period, cost or scheduling constraint that still needs confirmation.

Treat historical photos and attachments as their own record category. Ask how each file will remain connected to the right customer, location and job, and how the intended user will retrieve it. A filename appearing in a spreadsheet is not a test that the actual image opens. Try a representative file through the agreed destination or archive, with the access the team will actually use. If that path is unresolved, keep the file in the exception list; do not assume that a successful contact import brought the job photos with it.

If a provider says that migration is supported, ask for the scope in writing. Do not turn “customer import” into “everything transfers” in your internal plan. Keep the transfer plan separate from your product and price comparison: an attractive subscription does not establish that the proposed move works for your records.

Where ThePocketBoss customer imports fit

ThePocketBoss has a customer-list importer for supported Jobber and QuickBooks CSV exports. Its preview reports planned customer updates, new customers, already-imported records and existing duplicate pairs before the import is committed. Review those categories separately: an updated customer and a newly created customer are different results.

Customer matching uses email, phone and normalized-name checks. A shared contact detail is not a promise that two records represent the same person. The importer has specific handling for overlapping and existing duplicate records; it does not guarantee a duplicate-free CRM. Check the preview against your source and resolve uncertain identities before moving the full list.

For a handyman with repeat customers, this makes the customer list a practical first category to assess. In the fictional test below, check whether a repeat customer's identity and service locations remain understandable before relying on the next visit's details. Use the ThePocketBoss contractor CRM overview to evaluate customer management, and keep job history, old invoices, photos and connected accounting in their own transfer checks. This customer-import feature does not establish that those other records transfer with the same file.

Preserve the source and choose one input for each category

Save an unchanged source copy in a business-controlled location before preparing a working copy. Record the export time, filters used and any files included. Restrict access to the people who need the records. Do not paste customer lists or private job notes into public examples, shared support threads or an unapproved AI service.

Use one agreed source for a given import category. If customer records already exist in two connected systems, uploading both without checking the overlap may create a problem that looks like extra customers rather than duplicate input. Housecall Pro's import preparation guide specifically warns against importing the same data from both QuickBooks and the current software. Treat that as a documented warning for that workflow, not proof of how every product handles duplicates.

On the working copy, map fields before changing values. A billing address and a service address may look similar while serving different purposes. Keep a customer's identity connected to the right property and job. Mark ambiguity for review rather than guessing from a familiar name.

Counts are a useful first check, but they are not the whole check. Two records can arrive with the expected count and still contain swapped addresses or missing notes.

Test a small sample with different cases

Choose records that exercise the details you actually use. A single uncomplicated contact cannot test multiple properties, missing fields, attachments or an open job. Use a provider-supported test environment where available. Confirm how testing can be isolated from real messages, bookings, invoices and integrations before proceeding.

The table below is an original fictional test log. The labels and results illustrate decisions; they are not an actual ThePocketBoss import test or a real customer's migration.

Do not interpret a partial pass as a completed migration. Save the result of the corrected test, including what changed and who checked it. If the proposed method cannot support a required workflow, reconsider the transfer scope or product choice before committing the rest of the business to it.

If the result says zero imported or the count is unexpected

Stop and record the result before trying another full upload. Note which source file and sheet were selected, the intended record category, the time of the attempt and the exact status or error message. Keep the original export unchanged. Do not assume the cause is a particular row limit or a formatting error from the message alone.

Review the provider's current requirements against the working file and any validation results it supplies. Identify the unresolved difference, then ask support what to check and how to handle records that may already exist. A support request can describe the workflow and error without exposing a complete customer list. If a file is needed, confirm the approved private channel and limit it to what is necessary.

Housecall Pro's import and export guide advises users with incorrectly imported data to contact support rather than deleting and reimporting it themselves. Follow the destination provider's current recovery process; this checklist does not establish that a retry is safe or that another product offers the same recovery option.

Decide where changes will be recorded during the move

Write a short transition note that answers: when was the source taken, which system is authoritative for each active workflow, who is recording changes, and how will changes since the export be checked?

Avoid leaving the office and field crew to discover the boundary themselves. One person adding a visit to the old calendar while another changes it in the new app creates a reconciliation task. Decide how to capture such changes before the move starts.

Keep notifications and connected systems in the test plan. Do not activate an integration or run two message workflows merely to see what happens to real customers. Confirm with the relevant provider how reminders, accounting connections and other external actions should be handled during your particular transition. This checklist does not establish that a switch is reversible or that imports can be safely undone.

A scheduling capacity worksheet can help the team review the next day's workload after the data has been verified. It does not replace checking the migration itself.

Reconcile the working result before closing the old path

After the agreed transfer, compare the result with the source and the change log. Check record counts by category, then examine important field values and relationships. Ask the people who use the information to complete a representative task in the new workflow.

Can the office locate the correct customer? Can the assigned person find the job and its notes? Can a reviewer retrieve the original document that supports an unresolved question? For financial records, have the appropriate record owner or qualified adviser validate the treatment; a count of imported invoices does not certify balances or accounting accuracy.

Keep an exception list with the record identifier, problem, responsible person and next check. Do not repeatedly upload the same full file as a general repair without understanding the destination's update and duplicate behavior.

Only retire an old access path after confirming the information and retrieval you need, the remaining unresolved work and the applicable provider terms. There is no universal number of days in this checklist. The useful endpoint is an agreed, checked working arrangement, not the moment an upload progress bar finishes.

Use the result to make the switching decision

Passing the selected test gives you a record of what worked for those cases, what remained manual and what the team still needed to learn. It does not validate every record or workflow. A failed test is also useful: it identifies a missing field, unsupported document or unresolved workflow before a broader move.

When evaluating contractor business software, bring this evidence to the trial. Keep product selection separate from assumptions about automatic data transfer.

The next action is small: select one important record category, identify its source and destination handling, and write down what a correct result would look like. Test that result before planning the full move.