Migrate from ServiceMonster to Twenty CRM

ServiceMonster customer records (individual contacts at service businesses) map directly to Twenty People. The email, phone, name, and address fields transfer 1:1. ServiceMonster customers linked to a company map to People with the companyId relation set to the matching Twenty Company record.

ServiceMonster stores a customer's business entity as a company record. This maps to Twenty Companies with name, domain/website, industry, employee count, and address fields preserved. Parent-child company hierarchies in ServiceMonster map to the Twenty Company relation field. If ServiceMonster stores multiple contacts per company, each individual maps as a separate People record linked to the same Company.

ServiceMonster job records carry status, assigned technician, service address, line items, and completion notes. These split across Twenty's Opportunity object (stage = job status, amount = invoice total) and a custom Job object for service-specific fields like technicianId, serviceLocation, and completionNotes. We create the custom Job object in Twenty before migration.

ServiceMonster job statuses (Scheduled, In Progress, Completed, Cancelled) map to Twenty Opportunity stage values. We define a stage set in Twenty that mirrors your ServiceMonster job lifecycle — each stage maps value-by-value and probabilities are assigned per stage for forecasting continuity.

ServiceMonster invoices (line items, payment status, totals, payment dates) have no native equivalent in Twenty. We create a custom Invoice object in Twenty with fields for invoiceNumber, amount, status, paidDate, and a relation to the originating People record. Invoice line items become InvoiceLineItem child records under each Invoice.

ServiceMonster estimates map to a custom Estimate object linked to the relevant People and Company. Each estimate line item becomes an EstimateLineItem record. If the estimate converts to a job in ServiceMonster, that relationship is preserved via the Opportunity linked to the original Estimate.

ServiceMonster price list items (service codes, descriptions, area-based pricing units, consumables) migrate as a custom PriceListItem object in Twenty. Unit types and pricing formulas map to custom fields — area-based pricing units (sq ft, gallons) are preserved as custom field text values for reference.

ServiceMonster technician and staff records map to Twenty Workspace Members. Email matching is used to associate ServiceMonster owner/technician IDs to Twenty user accounts. If a technician has no email in ServiceMonster, we map them to a placeholder and flag for your admin to resolve.

ServiceMonster routes and schedule assignments (technician → route → jobs per day) have no Twenty equivalent. We create a custom Route object with fields for routeName, technicianId, scheduledDate, and a multi-relation to associated Job records. GPS check-in/check-out logs are preserved as custom date-time fields on the Route record.

ServiceMonster job photos and file attachments are preserved. We store the original file URL in a custom field on the associated Job record. If files are hosted in ServiceMonster's storage and you need full transfer, we re-upload them to Twenty's file storage or a linked cloud bucket.

ServiceMonster job completion notes and general notes map to Twenty Notes attached to the relevant People, Company, or Job record. Original timestamps and author attribution are preserved in the Note record's metadata. If a ServiceMonster note references another record (e.g., a job note linking to a customer), the Note is attached to the primary record and cross-referenced in the migration audit log.

Any custom fields configured in ServiceMonster on customers, jobs, invoices, or price lists migrate as custom fields on the corresponding Twenty object. Field types are evaluated at migration planning — pick-lists become Twenty select fields, text fields map to text, and numeric fields map to number types.