Migrate from SortScape to Twenty CRM

SortScape Customer maps to Twenty People. First name and last name concatenate into Twenty's displayName. Email, phone, and address fields map to their Twenty equivalents. The SortScape customer ID is stored as Source_System_ID__c on the Twenty record for traceability. If a customer record lacks a last name, the first name populates displayName with a trailing space preserved for consistency.

SortScape Customer records that represent businesses (not individuals) merge into Twenty Companies. The customer name becomes the Company displayName. Address data from SortScape maps to the Twenty Company address fields. Individuals without a business name land as People records only.

SortScape Job maps directly to Twenty Opportunities. Job title becomes the Opportunity name. Job status (scheduled, in-progress, completed, cancelled) maps via value_mapping to Twenty Opportunity stage values. Job amount and estimated cost migrate as the Opportunity amount. SortScape custom fields (job_type, priority, service_items) require Twenty custom fields.

SortScape stores route-optimization coordinates on Jobs. These migrate as custom lat/lng text fields on the associated Twenty Company record. Twenty has no native routing engine; the coordinates are preserved for use with external mapping tools post-migration. The coordinate fields are labeled Route_Latitude__c and Route_Longitude__c for clear identification during import and reconciliation.

SortScape Visit maps to Twenty Task. The visit's scheduled start/end time becomes the Task due date. Visit notes, visit status, and assigned staff member map as custom fields on the Task. The parent Job maps via OpportunityId so the task is linked to the correct deal in Twenty.

SortScape Staff member name and email map to Twenty WorkspaceMember. Email is used as the unique identifier. Staff without a matching email in Twenty are flagged before migration; records can be reassigned to an existing Twenty user or left unassigned pending team invitation.

SortScape notes on jobs or customers migrate as Twenty Notes attached to the corresponding People or Opportunity record. File attachments (photos, signed documents) store as custom URL fields on the related Twenty record pointing to the exported file URL. Notes inherit the created date from SortScape where available, preserving the original context timeline.

Twenty's createdAt timestamp reflects the import date. SortScape's original job creation date is stored as Original_Job_Create_Date__c custom datetime for reporting continuity and audit purposes. This preservation allows you to run reports on job creation patterns over time, analyze seasonal trends from the source data, and maintain a complete audit trail without relying on Twenty's system-generated timestamps alone.

SortScape customer tags (landscape, maintenance, one-time) migrate as a custom text field on the Twenty People record. Twenty does not have a native tags array on People; the field is exported as a comma-separated string for reference. The custom field is named SortScape_Tag__c and appears in the People record detail view for quick filtering.

SortScape's Xero invoice ID stored on a Job migrates as Xero_Invoice_Ref__c on the Twenty Opportunity. The field is informational only; Xero reconnection is a post-migration step that requires your Xero admin to re-authorize the integration in Twenty. After reconnection, invoice links can be rebuilt by matching the Xero_Invoice_Ref__c value against Xero's API.

SortScape automated reminders tied to visit scheduling and job-status changes have no equivalent in Twenty's workflow builder. We export SortScape workflow definitions as a reference JSON. Your Twenty admin rebuilds these as workflow triggers on the Opportunity object using the task due date as the trigger condition.

SortScape's route-optimization engine and saved route configurations are proprietary to the SortScape scheduler and cannot be extracted. Start/end addresses for each job visit migrate as Company address fields and Task notes. Route planning must be rebuilt using a dedicated routing tool or external optimization service post-migration.