Migrate from Kickserv to Twenty CRM

Kickserv Customers map 1:1 to Twenty Companies. Company name, domain, address, city, state, zip, country, industry, and employee count all have direct Twenty Company equivalents. Multi-location customers require a parent-company / child-company rule in the migration plan. Address fields may be split into street, city, state, and zip, so verify that each component aligns with Twenty's required format before import.

Kickserv Contacts map 1:1 to Twenty People. Each contact's name, email, phone, mobile phone, job title, and address fields migrate directly. Contacts without a primary customer link land as People with no companyId and are flagged for review. These orphaned records are logged in the migration audit report, and your admin can manually assign them to the correct company after import.

Kickserv's contact-to-customer association becomes a companyId relation on Twenty People. The contact's role on the Customer (e.g., Primary, Billing) maps to a custom role field on the People record. If a contact has multiple Customer associations, the primary (most recently modified) wins as companyId.

Kickserv Jobs are the core unit of work — they carry status, type, scheduled time, assigned employee, customer link, and line items. Twenty Opportunities store deal data with stage, amount, probability, and close date. Job name becomes Opportunity name; job status pick-list values map to Opportunity custom-stage fields; work order number and job type migrate as custom fields.

Kickserv job statuses (Unscheduled, Scheduled, In Progress, On Hold, Completed, Cancelled) have no direct Twenty equivalent. Each value becomes a custom pick-list option on a Job_Status__c custom field. The mapping table is delivered with the migration plan for admin review before migration runs.

Kickserv job types (Repair, Maintenance, Installation, Inspection, etc.) become a Job_Type__c custom pick-list on Twenty Opportunities. If Kickserv uses free-form type text rather than a pick-list, the unique values are enumerated during audit and created as pick-list options in Twenty before import.

Kickserv Events (scheduled work blocks with start/end time, employee assignment, and job link) migrate as Twenty Tasks. Event subject becomes Task subject, start time becomes due date, and the job link becomes a custom field (Related_Job__c) since Twenty Tasks can link to People, Companies, and Opportunities but not directly to custom objects.

Kickserv Employees map to Twenty WorkspaceMembers. Owner-resolution in Opportunities and Tasks uses email match: each Kickserv employee email is matched to a Twenty user by email address. Unmatched employees are flagged before migration — your team either provisions them in Twenty first or assigns their records to a fallback owner.

Kickserv Estimates and Invoices have no direct Twenty CRM equivalent. These migrate as a custom object (if your Twenty plan supports it) or as Opportunity custom fields storing the latest estimate/invoice amount, number, and status. Line items are not structurally migratable — they are referenced by estimate/invoice number.

Kickserv Notes on Customers, Contacts, or Jobs migrate as Twenty Notes attached to the corresponding Company, People, or Opportunity record. Rich-text formatting in Kickserv Notes is preserved as HTML in Twenty Notes. If the original notes contain file attachments, those files must be exported separately and linked manually in Twenty, as the note migration transfers text content only.

Kickserv Time Entries track employee hours on jobs. Each time entry becomes a Task with custom fields for hours logged, billable/non-billable flag, and linked job reference. The Kickserv time-entry total hours are stored on the related Opportunity custom fields for reporting.

Kickserv custom fields on Jobs, Customers, and Contacts map to custom fields on Twenty Opportunities, Companies, and People respectively. All custom fields must be created in Twenty Settings → Data Model before import — the CSV import creates records, not fields. FlitStack delivers a custom-field creation checklist with the migration plan.