Migrate your The Service Program data

Customers sync bidirectionally with QuickBooks via the one-click sync feature. We export Customer records as a standard CSV or via direct QuickBooks export and map them to the destination CRM's Contact or Account object. Address, phone, and email fields carry over cleanly.

Work Orders are the core TSP object and hold job details, scheduling, technician assignments, and status. TSP has no standalone export API — we extract Work Order data via direct Windows-database access or CSV preparation from within the desktop application, then map fields to the destination system's equivalent object.

Technician profiles store certifications, assignment history, and routing data. We map technician records to Users or Contacts in the destination system and preserve assignment linkages to Work Orders during migration.

Tasks and subtasks nested under Work Orders capture job steps and progression. We flatten the task hierarchy into the destination system's task or sub-item structure and preserve parent Work Order associations.

Time and expense tracking supports timesheet management and billing. We map time entries to the destination system's time-tracking object, preserving billable/non-billable flags and linking them to the migrated Work Order.

Vendor management data syncs through QuickBooks as part of the vendor master. We export via QuickBooks and map to the destination system's Vendor or Supplier object, flagging any TSP-specific vendor metadata that does not map directly.

Warranty tracking links to customer assets and equipment records. We preserve warranty duration, expiration dates, and obligation terms as custom fields on the migrated Customer or Asset object in the destination system.

TSP generates route plans and maps for field technicians. These are stored as TSP-specific scheduling data rather than a standard object. We extract route assignments and schedule windows and map them to calendar or scheduling constructs in the destination system.

TSP supports customizable fields for business-specific workflows. We audit custom field configurations during scoping, export their definitions alongside record data, and recreate them as custom properties in the destination system.

SMS messaging history is a transactional log within TSP's communication module and is not exposed via export or API. We do not migrate SMS records — we document this gap and advise customers to export communications separately if required for compliance.

The QuickBooks sync configuration itself — mapping rules, sync direction, and sync frequency — lives in TSP's local settings and is not transferable to a new system. We treat it as a decommissioned configuration and do not migrate it.