Migrate from Workiz to Twenty CRM

Workiz Clients map directly to Twenty People. Name, email, phone, address, and job title transfer as-is. The client-company distinction in Workiz (flat list) maps to Twenty's People object with a companyId relation to Companies. If a Workiz client represents a business entity, create a Company record and link the Person to it via companyId.

Workiz clients that represent companies rather than individuals (such as property management firms, commercial clients, or business-to-business service providers) migrate to Twenty Companies. Company name, domain, address, and industry map directly to Twenty's standard Company fields. For organizations with multiple service locations, each distinct address generates a separate Company record to preserve location-specific context and maintain accurate relationship mapping between people and company entities.

Workiz Jobs are the core entity with status, type, scheduled times, assigned technician, and client link. Twenty has no native job object. We create a set of custom fields on the Opportunity object: job_status (select), job_type (select), scheduled_start (datetime), scheduled_end (datetime), assigned_tech (text), and work_order_number (text). The Job-Client relationship becomes Opportunity linked to People via the opportunityPersonId field.

Workiz Leads map to Twenty People records, since Twenty does not have a separate Lead object. Lead name, email, phone, source, and status migrate as Person fields. The lead's company name creates a linked Company record if it does not already exist. Historical lead score or rating data migrates as a custom number field.

Workiz Estimates have line items, totals, status, and expiration dates. Twenty has no native estimate object. Estimates migrate as Opportunities with custom fields for estimate_number (text), estimate_status (select), and expiration_date (date). Line items reference a custom Items object. The Opportunity Amount field is populated from the estimate total.

Workiz Invoices have invoice number, status (draft/sent/paid/overdue), issue date, due date, total, balance, and line items. Twenty has no native invoice object. We create a custom Invoice__c object in Twenty with fields for invoice_number, status, issue_date, due_date, total_amount, balance_due, and payment_method. Line items reference a custom Items object.

Workiz Items store products and services with name, description, unit price, SKU, and item type (product/service/part). Twenty has no native product catalog. We create a custom Item__c object with name, description, unit_price (number), sku (text), and item_type (select). Items are linked to Invoice__c and Estimate Opportunity records via relation fields.

Workiz custom fields attach to Jobs, Clients, Leads, Estimates, Invoices, and Items. Each Workiz custom field is recreated as a custom field in Twenty's Data Model (Settings → Data Model) on the corresponding object. Pick-list fields in Workiz require value-by-value setup in Twenty's select options before import. Custom fields must be created before CSV import or the import will not populate them.

Workiz stores call logs with subject, duration, direction (inbound/outbound), and timestamp linked to the client or job. These migrate as Twenty Tasks with Type = 'Call', the original subject, start time, and duration. The Task is linked to the corresponding Person or Opportunity record. Original call owner resolves to Twenty Workspace Member by email.

Workiz users (dispatchers, admins, field techs) become Twenty Workspace Members. Resolution is by email match. Workiz owner_id on Jobs and Estimates maps to Twenty Workspace Member via email lookup. Workiz technicians who should not access the CRM are flagged during planning — their records are assigned to a fallback owner in Twenty.

Workiz files attached to Jobs (photos, documents, signatures) are downloaded and re-uploaded to Twenty. Twenty stores files in its file storage system and attaches them to the relevant Opportunity record. File size limits apply — Workiz files over Twenty's storage limit are flagged for compression before re-upload.

Workiz automations are trigger-action rules scoped to job-state events (e.g., 'When job status changes to Scheduled, send SMS to client'). Twenty has a separate workflow system with different trigger/action architecture. Automations cannot be exported from Workiz in a transferable format and must be rebuilt manually in Twenty's workflow builder. We provide an automation audit document listing every active Workiz rule for your team to reference during the rebuild.