Migrate from Summit Service Systems to Twenty CRM

Summit Customer records map directly to Twenty People objects. Each Person record preserves the customer's contact details, service address, and primary technician assignment. The original Customer ID is stored in a custom Source_System_ID__c field on the People record for traceability, relationship mapping, and delta-run de-duplication against future sync runs.

Summit Company records map one-to-one to Twenty Companies without transformation. The primary service address from Summit maps to the Company address field in Twenty. For multi-location accounts where Summit stores multiple service addresses per company, a custom Locations object must be created in Twenty with a lookup relationship back to the parent Company, allowing each location to be tracked independently while remaining linked to its organization.

Summit Work Order becomes Twenty Opportunity. Work order status (Scheduled, In Progress, Completed, Cancelled) maps to a custom Opportunity Stage field. Service address becomes the Opportunity address; technician name becomes the Opportunity owner resolved by email match against Twenty workspace members.

Summit work order status pick-list values map to a custom Stage__c field on Twenty Opportunities. Before migration, each Summit status option — such as Scheduled, Dispatched, On-Site, and Completed — is configured as a pick-list value in Twenty's data model under Settings. This ensures work orders migrate with their status correctly mapped to the matching option in Twenty without data loss or rejection due to invalid field values.

Summit service contracts (with renewal dates, terms, and coverage scope) have no native Twenty equivalent. We create a ServiceContract custom object in Twenty with fields for contract term, renewal date, and coverage type. The custom object links to the related Company record via a lookup relationship.

Summit service reminders map to Twenty Tasks. The reminder date becomes the Task due date, the technician becomes the Task assignee, and the related Work Order link is preserved. Task status is set to Open on import and marked Complete once the related Opportunity stage reaches Completed.

Summit inventory items tracking parts and equipment do not map to Twenty's standard objects. We create an InventoryItem custom object with fields for part number, description, quantity on hand, and reorder level. The object links to related Work Orders through a lookup relationship.

Summit stores multiple service locations per customer. We map the primary service address to the Twenty Company address field. Secondary locations are stored in a custom Address2__c field or a separate custom Locations object if your team requires granular multi-site visibility in Twenty.

Summit billing and invoice records have no native Twenty equivalent. We migrate invoice number, total amount, payment status, and billing date as read-only custom fields on the related Opportunity. The financial data is preserved for reference but Twenty does not generate invoices.

Summit file attachments on work orders — including photos, diagrams, and signed forms — are migrated as Twenty Notes attached to the corresponding Opportunity record. Each Note is linked to the work order's Opportunity in Twenty, preserving the attachment context. Standard Twenty file size limits apply to uploaded content, and inline images are rehosted as external links to avoid bloat in the Twenty workspace while maintaining accessibility.

Summit technicians and staff map to Twenty workspace members. Resolution happens by email match — each Summit technician with an email address is matched to a Twenty user by email. Technicians without email addresses are flagged before migration and assigned to a fallback Twenty user.

Summit custom fields on any entity are created as custom fields in Twenty's data model under Settings → Data Model before migration runs. Field type is preserved (text, number, date, select) and validated against Twenty's supported field types. Custom fields must exist before records import.