Migrate from ServiceTracker to Twenty CRM

Twenty lacks native field-service dispatch and scheduling features

ServiceTracker's core value is dispatch, route optimization, and technician scheduling. Twenty CRM has no equivalent — scheduling constraints, route preferences, and availability windows do not have a native construct. We map the technician assignment and service date, but dispatch rules and scheduling logic must be rebuilt as Twenty workflow automations or handled by a separate scheduling integration after migration. FlitStack can export your ServiceTracker dispatch rule definitions as a rebuild reference for your Twenty admin.

Twenty's CSV import caps at 20,000 records per file

ServiceTracker setups with large service-history volumes can exceed Twenty's per-file CSV import limit. We handle this by splitting exports into 20,000-record batches and running staged imports with relationship resolution between batches. For migrations exceeding 50,000 records with complex activity logs, we recommend the Twenty API import path (100 req/min on Cloud Pro) for better throughput and error tracking. The Organization tier raises this to 200 req/min. Large customers with 100,000+ records across all modules typically benefit from API-based imports to maintain data integrity and reduce manual intervention during the migration window.

Work-order status to Opportunity stage mapping requires pre-migration value setup

ServiceTracker work-order status strings (Open, In Progress, Completed, Cancelled) map to Twenty Opportunity Stage pick-list values, but those stage values must exist in Twenty before the migration runs. If your Twenty workspace uses non-standard stage names, we need the exact stage string list in advance. We deliver a stage-mapping spec before the migration run so your admin can create or rename stages in Twenty's pipeline settings. This coordination ensures that status values map correctly during the import process and prevents data quality issues in your Twenty Opportunities.

Signature and parts data migrate as Note text, not structured fields

ServiceTracker signature captures and parts-used lists have no direct equivalent in Twenty's standard object model. We migrate them as Notes attached to the Opportunity, storing the signature URL or parts list as structured text in the Note body. If you need these as structured data rather than free-text notes, we create a custom WorkOrder object with signature and parts fields before migration — this requires additional schema setup time and is scoped separately.

Technician-to-WorkspaceMember email resolution can fail for inactive ServiceTracker accounts

We match ServiceTracker technicians to Twenty Workspace Members by email. Technicians who have left your organization and no longer have a Twenty user account will not resolve. We flag all unmatched technicians before migration and assign their work orders to a fallback owner (your specified admin or a generic Unassigned record). Active technicians with email mismatches require manual correction after migration. If a technician has multiple email addresses in ServiceTracker, we attempt matching on each before flagging as unmatched. You can also choose to create placeholder Workspace Members for all technicians before migration begins to ensure complete coverage.