Job management software implementation and data migration checklist

Choose the first working process

Define a specific starting workflow, such as receiving an Enquiry for an existing Customer, locating the Site and preparing a draft Quote. Name the people who perform each step. A broad objective to "move everything" does not tell you which record relationships the first rehearsal must preserve.

Separate the required launch workflow from later improvements. Accounting connections, recurring work or historical document import may have different support and setup requirements. Confirm what is available rather than making an unverified capability a dependency for the first working day.

Assign an implementation owner and an actual reviewer for the sample. The owner coordinates the decisions; the reviewer checks whether the result supports the work. A person familiar with the source data can recognise a mismatch that a row-count check would miss.

Record the acceptance criteria before preparing the file. Examples include finding the correct Customer, preserving a postcode and locating the selected work context. Avoid declaring success solely because the software displays an import-complete message.

Inventory what will move and what will remain accessible

List the source systems, record types, approximate volumes, relevant date ranges and who can export them. Customers, company contacts, Sites, active work, issued documents and payment records have different meanings. Do not combine them into one spreadsheet just because they all contain a name.

For each type, identify the supported destination route. That may be an importer, a reviewed manual process or retained access to the historical source. A customer importer does not establish support for open Jobs, issued Invoice versions or allocated payments.

Current vendor documentation demonstrates why the route needs checking. Tradify’s customer-import guide describes matching existing customers by name and updating mapped non-blank fields. Fergus describes its own customer CSV mapping. Those are product-specific behaviours, not a universal rule for another destination.

Record the decision for material that will not be transferred. The team needs a reliable retrieval route for retained history and a clear boundary between old and new working records. An unavailable archive can leave a clean new directory unable to answer a customer’s earlier-work question.

Clean and map without losing the record’s meaning

Make a controlled working copy of the authorised export and retain the source reference. Review duplicates, incomplete identities, outdated contacts and inconsistent address fields. A tidy label is helpful, but merging two people because their names look similar can create a more serious error than untidy spelling.

The mapping table records the source column, destination field, meaning, transformation and sample check. Distinguish a Customer’s billing address from a property where work happens. Confirm how company contacts and relationships are represented rather than placing every person in one undifferentiated name field.

Check formatting through the actual export and import route. Microsoft explains that Excel can interpret CSV columns using default formats, including date formats and numbers with leading zeros. Inspect UK phone numbers, postcodes, references and unambiguous dates after conversion instead of trusting the spreadsheet’s visible appearance.

Microsoft also notes that saving to a text format saves the current worksheet, with features potentially lost. Confirm which sheet and values you exported. A workbook containing formulas, notes and several tabs is not automatically preserved in one CSV file.

Keep unsupported or uncertain values in the decision log. Do not invent placeholder dates, classify unknown tax information or turn an unclear customer relationship into a confirmed one simply to pass a required-field check. Identify the actual information needed and who supplies it.

Rehearse a small representative transfer

Use an appropriate test environment or supported preview with a small authorised sample. Include a new Person Customer, a Company, a possible duplicate and a record needing a decision. Test the difficult shapes you actually have rather than selecting only complete rows that cannot expose a problem.

The pack’s four-row exercise contains one existing Company to reuse after confirmation, two new Customers to create and one ambiguous name to hold for review. Its expected outcome is two creations, one reuse and one unresolved row. The source count of four is not a target of four new Customers.

Record each source row’s decision and destination reference. Where a relationship needs a separate step, record that outcome too. Finding the person in the directory does not prove their company relationship, selected contact or work association was transferred.

Inspect values and behaviour after the rehearsal. Search the relevant property or Customer, open the record and compare the selected fields with the source. Check whether a possible duplicate was reused, updated, skipped or created according to the actual destination process.

Do not rerun an uncertain import blindly. First establish what the earlier attempt created or changed and how the destination supports correction or retry. A second upload can compound duplicates or overwrite reviewed values if its behaviour is misunderstood.

Reconcile counts, fields and relationships

Start with the row decisions: source rows equal created, reused, excluded or unresolved rows under your defined categories. Then inspect the resulting distinct records. A balanced count is useful evidence, but two misassigned names can still make the arithmetic balance.

Check a field sample for exact meaning, not merely whether it is populated. Inspect address components, phone formatting, Person or Company identity and the current contact position. A value copied into the wrong field can look complete while causing the next task to fail.

If work or financial records are part of the supported transfer, reconcile their own references, status and amount basis with the relevant reviewer. Customer-row counts cannot prove that an outstanding Invoice, accepted Quote or recorded receipt retained its correct state.

Use representative roles and devices for the workflow test. A record visible to the implementation owner may not be available to the team member using it. Confirm appropriate access and useful work context without assuming that more visibility is the solution to every missing record.

Plan the changeover and exceptions

Choose the source cut-off and explain where changes will be recorded during the transfer. Otherwise a customer update made after the export can be lost between systems. Keep any intervening changes in a controlled log for review against the destination.

Prepare a changeover decision with the sample results, unresolved items, support route and the conditions for proceeding or postponing. Preserve access to necessary source evidence. Avoid irreversible cleanup until the actual transfer and operational handover have been reviewed.

Select the live communication settings deliberately. Migrating a contact does not authorise sending a message, resuming a reminder or inviting an account. Review those separate actions through the relevant business process, using a rehearsal that does not accidentally contact customers.

Give the team a short operating note: where to find current work, where retained history lives, who resolves an exception and which system owns new updates from the cut-off. Conflicting working copies can undo an otherwise careful migration.

Accept the working result

Have the relevant people perform the defined first workflow and record the result. Confirm the useful field checks, record relationships, permissions and exception route. A completed training session is not the same as demonstrating that the team can use its transferred records.

Review the first live batch against the rehearsal expectations and log any correction through the appropriate process. Assign a follow-up review for the outstanding items. The completed implementation pack should explain what moved, what was checked, what remains available elsewhere and who owns the next decision.