Migrate from Metis CRM to Twenty CRM

Metis Client records map directly to Twenty Company. The Client's name, address, contact email, and phone fields map to Twenty's Company standard fields. We use Client name as the dedupe key during import. Company is the first object inserted because People and Opportunities both carry a Client lookup that must be resolved before child record import.

Metis People records map to Twenty Contact. We extract role, contact details (email, phone, address), and the linked Client to resolve the Twenty Company foreign key. The Person's name fields map to Contact's display name and email. Role information migrates to a custom Contact field or the job title standard field depending on the customer's scoping preference.

Metis Opportunity records map to Twenty Deal. Stage, value, and close date transfer directly. The Opportunity's linked Client resolves to the Twenty Company that was created first in the import sequence. Pipeline in Metis maps to a Twenty pipeline that we configure during schema setup before migration begins.

Metis Jobs are project records with job costing, status, and dates. They map to Twenty Deals with a custom field job_type__c set to 'project' to distinguish from Opportunities in the same pipeline. Job costing fields migrate to custom Deal fields. We run Jobs after Opportunities in the import sequence because both are child objects of Client but Jobs may carry richer cost data that the customer wants visible in Twenty reporting.

Metis Timesheet entries map to Twenty Activity records. Billable time entries with a linked Job map to Task records with the Job's Deal as the WhatId. Non-billable entries map to Event records. Duration, date, and billable flag transfer to Task or Event fields. Timesheets without a linked Job (orphan entries) go to a reconciliation queue before migration; the customer chooses to assign them to a default placeholder Deal, skip them, or create placeholder Deals.

Metis People Expenses map to a Twenty custom object (expense__c) with fields for amount, date, category, and person reference. Receipt images do not embed in the CSV export and migrate via parallel file transfer. Each expense record in the migration log carries a image_reattachment note instructing the customer to re-link the receipt file in Twenty after migration. We do not use the Xero-friendly People Expenses export variant as a migration source; we extract the standard zone CSV and handle Xero mapping as a separate destination-side concern.

Metis Central Expenses (agency-level overhead) map to the same Twenty expense__c custom object with an additional field expense_scope__c set to 'central' to differentiate from People Expenses. Receipt images handle identically to People Expenses — parallel file transfer with re-attachment notes in the migration log.

Metis People records tagged as team members (not just clients) map to Twenty User accounts. We resolve by email match. If a matching Twenty User does not exist, the record is held in the Owner reconciliation queue and the customer provisions the User before record import resumes.

Metis Resourcing Reports are filtered views combining People availability with Job assignments — not transactional records. The underlying data (People, Jobs, time allocations) migrates separately. Twenty has no native resourcing view; the community recommends pairing with Metabase or another BI tool for utilization reporting. We flag this gap in the migration inventory and describe the data sources available for rebuilding the report in a BI layer.

The Xero-friendly export format is a destination-specific schema variant designed for direct Xero import. It is not a general migration source format. We extract the standard People Expenses zone CSV and handle any Xero mapping as a separate transformation step if the customer requires it.