Migrate from Service Toolz to Twenty CRM

Service Toolz contacts migrate as Twenty People records. Email, phone, address, and job title map directly. The primary company link in Service Toolz becomes the companyId relation in Twenty. Original create timestamps are preserved as a custom datetime field since Twenty's createdAt is set at migration time.

Service Toolz company records migrate as Twenty Companies. Domain, industry, employee count, and annual revenue map to their Twenty equivalents. Parent-company hierarchies in Service Toolz map to Twenty's companyId self-reference. Companies must migrate before People to satisfy Twenty's import-order constraint.

Service Toolz quotes map to Twenty Opportunities. Quote name becomes Opportunity name. Quote amount maps to amount. Quote status (Draft, Sent, Accepted, Lost) maps to Opportunity stage via value mapping. The linked contact and company from the quote become the Opportunity's personId and companyId relations.

Service Toolz work orders are the most complex migration object. Work order status, priority, scheduled date, and service type become Twenty task fields. The assigned technician email resolves to a Twenty workspace member. Work order line items (parts, labor) require either a custom task description format or a ServiceItems custom object with a relation to the task.

Service Toolz line items attached to work orders (part number, quantity, unit price, labor hours) do not map to any native Twenty field. We create a ServiceItem custom object with fields for itemType, partNumber, quantity, unitPrice, and laborHours, then create a one-to-many relation from the target Task to ServiceItem records.

Service Toolz technician records contain name, email, phone, certifications, and availability status. These map to Twenty workspace members: name and email are required, phone migrates as a custom field, certifications migrate as a text array or multi-select custom field. Availability status has no direct Twenty equivalent — it's preserved as a custom field for reference.

Service Toolz inventory (part numbers, stock levels, reorder points, bin locations) has no equivalent in Twenty's standard objects. We create an InventoryItem custom object with partNumber, stockQuantity, reorderPoint, binLocation, and unitCost fields. Inventory records link to Companies as a vendor relation.

Service Toolz invoices include invoice number, amount, status, line items, and payment history. Twenty has no native invoicing. Invoice data migrates as read-only InvoiceReference custom object records — invoice number, amount, status, date, and linked companyId are preserved for historical reference. The payment transaction history migrates as Note records attached to the InvoiceReference.

Service Toolz custom properties on any object migrate to Twenty custom fields created via Settings → Data Model before migration runs. Custom field data type mapping: text → TEXT, number → NUMBER, date → DATE, dropdown → SELECT, checkbox → BOOLEAN, multi-select → MULTI_SELECT. Pick-list values require value-by-value mapping.

Service Toolz file attachments on contacts, companies, and work orders re-upload to Twenty's attachment model. Files attach to the migrated record they were associated with in Service Toolz. Inline images in notes are extracted and re-hosted as Twenty attachments. File size limits from Service Toolz's storage tier apply.

Service Toolz notes attached to any record migrate as Twenty Notes. The note body, create timestamp, and author (by email lookup to workspace members) are preserved. Notes attach to the target People, Company, or Task record via the relation field. Rich-text formatting is preserved where Service Toolz supports it.

Service Toolz user records (dispatchers, admins, technicians) map to Twenty workspace members. Owner assignments on quotes and work orders resolve by email match to existing Twenty workspace members. Unmatched owners are flagged before migration — the team either creates the user in Twenty first or assigns records to a fallback workspace member.