FORGE
FORGE
Breadcrumbs

Signature Migration Tab

A practical, tenant-safe workflow for moving legacy Signature data into WennSoft Service.

Intended user

Tenant administrators who can access both Signature SQL data and Service Settings

Workflow

Export one dataset to CSV, upload it, verify success, then continue in dependency order

Important Prerequisites and Limitations

  • Service call costs: Before either Group 5 service-call-cost import, complete Units Of Measure Xrefs and confirm that every exported source UOM resolves to an existing Units Of Measure record in the same company and business unit.

  • Appointments: Rows whose duration_minutes and calculated_duration_minutes do not match are skipped and reported as row-level errors. The provided SQL helper handles cross-midnight end times and preserves legacy 15-minute rows.

  • Dependencies: Parent data and cross-references must resolve before dependent rows can be written. A failed row does not mean that every other valid row in the file failed.

  • Background processing: Uploads are asynchronous. Keep the task open long enough to confirm the queued status, then use the displayed migration status and correlation value to follow progress.

Before You Begin

  • Use a tenant administrator account.

  • Confirm the active company and business unit. Every upload applies only to that selected scope.

  • Have access to the legacy Signature SQL Server database and SQL Server Management Studio (SSMS) or prepare a CSV that matches the published dataset template.

  • Plan to upload one dataset per job. Do not advance to a later group until every dataset in the earlier group shows Succeeded.

Migration Procedure

  1. Open Signature Migration

In WennSoft Service, select Settings > Administration > Service Settings, then open the Signature Migration tab.

  1. Choose the next dataset

Start with Group 1 and work through the groups in order. Later groups remain unavailable until all datasets in earlier groups have succeeded.

Run Order

Group

Datasets to complete

Group 1

Call Types; Cost Categories; Departments; Equipment Types; Labor Rate Groups; Manufacturers; Positions; Problem Types; Rate Categories; Ship To Xrefs; Product Xrefs; Vendor Xrefs; Units Of Measure Xrefs; Warehouse Xrefs; Skill Levels

Group 2

Employees; Labor Group Billing Rates; Location Labor Rate Group

Group 3

Resource Technicians

Group 4

Employee Rates; Service Calls

Group 5

Appointments; Purchase Orders; Service Call Costs (Purchase Order Lines Received); Service Call Costs (Excluding Purchase Orders)

  1. Export the source data

Select the dataset card to open its upload window. For datasets with a SQL helper, select Copy SQL, run the copied query against the source Signature database, and save the results locally as a CSV file.

    • In SQL Server Management Studio (SSMS), set Tools > Options > Query Results > SQL Server > Results to Grid and enable Include column headers when copying or saving the results.

    • Run the query, right-click the results grid, select Save Results As, and choose CSV.

    • Do not rename, remove, or reformat the exported headers. Unknown extra columns may be ignored for some datasets, but required columns and values must remain present.

  1. Upload the CSV

Return to the dataset upload window and provide the CSV you just exported.

Complete the following fields:

    • CSV file (Required) - Choose the CSV for the dataset shown in the window. The visible label includes that dataset name, such as Manufacturers CSV or Service Calls CSV. Only .csv files are accepted. The file must include a header row and must belong to the active company and business unit.

    • Select Upload Data. The file is uploaded and the migration job is queued for background processing. Select Cancel if you need to correct the file before queuing it.

  1. Verify the result before continuing

Review the dataset card for its latest Status, Correlation, Processed/Inserted/Updated counts, and Last synced time. A Succeeded status means that dataset has completed for the active company and business unit.

    • Keep the correlation value available if you need support assistance.

    • If a job reports validation or row-level errors, correct the source or prerequisite data and upload the dataset again. Reruns update matching records rather than intentionally creating duplicates.

    • After every dataset in a group succeeds, continue with the next group.

Completion Result

The migration is complete when every required dataset in Groups 1 through 5 shows Succeeded for the intended company and business unit. Review the inserted and updated counts for reasonableness and retain the correlation values with your migration records.