Migrate from Markate to Twenty CRM

Markate Customers hold both company-level and contact-level data in a single record. We split each Customer into a Twenty Company record (for business name, address, and billing details) and a Twenty Person record (for the primary contact name, email, and phone). The Person is linked to the Company via the workspaceMember and personCompany relationships. We use the Customer email address as the dedupe key to avoid creating duplicate Person records when the same contact appears across multiple Markate records.

Markate stores service address and billing address on the Customer record. We map the primary service address to the Twenty Company address fields (addressStreet, addressCity, addressState, addressCountry, addressPostcode). If Markate stores separate billing and service addresses, we capture both in address fields and note the billing address in a custom field billing_address__c created in Twenty before migration.

Markate Estimates map to Twenty Opportunities with a custom field estimate_status__c carrying the Markate estimate status (sent, accepted, declined). The estimated amount maps to Opportunity amount. We create a dedicated Opportunity Stage called 'Estimate' in Twenty's sales process before migration so that Estimate records appear as a distinct pipeline stage in reporting. If the customer uses multiple pipeline stages in Markate, we map each to a Twenty Opportunity stage configured in Settings.

Markate Estimate line items reference Items from the catalog. We create a custom object EstimateLineItem in Twenty with fields for description, quantity, unit price, and total, and a lookup to the parent Opportunity (representing the Estimate) and the related Item. Items and Categories must be migrated first so that the Item reference is valid at line-item import time.

Markate Work Orders are the job ticket entity with job details, assigned team members, and schedule information. We create a custom object WorkOrder in Twenty with fields for job description, scheduled date, assigned team member (lookup to Twenty User), status, and any Markate custom properties surfaced in the CSV. Work Order status maps to a custom picklist matching Markate's statuses. The Task object in Twenty handles assignment and due date for individual action items derived from Work Order tasks.

Markate Invoices map to Twenty Opportunities with stage set to Closed Won and a custom field invoice_status__c holding the Markate payment status (paid, partial, outstanding). Invoice line items are migrated to the same EstimateLineItem custom object used for Estimates, linked to the closed Opportunity. Partial payment details are noted in custom fields invoice_amount_paid__c and invoice_amount_due__c.

Markate Items (products and services) map to a custom object Product in Twenty since Twenty's standard Product2 object is oriented toward commerce and may not fit field-service pricing models. We create the Product custom object with fields for name, sku, description, unit_price, and unit_type. Items must be migrated before Invoices and Estimates so that line-item lookups resolve correctly.

Markate Categories define groupings for Items. We map top-level categories to a custom picklist field category__c on the Product custom object. If the customer uses multi-level category hierarchies, we flatten them to a pipe-delimited string (e.g., 'HVAC | Repair | Compressor') and store in category_path__c. Category records without Items are flagged as orphans for the customer to review.

Markate Expenses track job-related costs linked to Work Orders or Customers. We migrate Expense records as Note records in Twenty linked via ContentDocumentLink to the related WorkOrder (custom object) or Company. The Note title carries the expense description and the Note body carries amount, vendor, and date. Receipt attachments are flagged as manual-upload items since Markate's Data Migration tool does not export files.

Markate Team Members are billable users assigned to Work Orders and Invoices. We map them to Twenty User records. The customer must invite all team members through Twenty Settings → Members before migration begins, per Twenty's requirement that referenced users exist before user-lookup fields can be populated. Team members without matching Twenty Users go to a reconciliation queue.

Markate does not expose custom field definitions via its CSV export, so any custom fields created by the customer in Markate are not visible in the exported data. We document this as a gap during scoping and work with the customer to identify which custom field values they need to preserve. Those values are re-entered or re-configured as custom fields on the relevant Twenty objects after migration. This is a manual step with no automated path.