Migrate from Metis CRM to Zoho CRM

Metis Clients map directly to Zoho CRM Accounts. Client name becomes Account Name, and any contact email on the client record becomes the primary account email. We extract from the Clients zone CSV export. The client identifier from Metis becomes the Zoho Account ID, and any client-level custom fields are mapped to Zoho custom fields on Account. Parent-client hierarchies in Metis map to Account hierarchies in Zoho if the customer has multi-tier client structures.

Metis People records map to Zoho CRM Contacts. The Person's associated Client from Metis resolves to the Zoho Account lookup on the Contact. Email, phone, role, and address fields map directly. We extract from the People zone CSV and resolve the account_id reference by matching the Metis Client name to the Zoho Account created in the prior phase. People without a client association map to Contacts without an Account link and are flagged for manual assignment.

Metis Opportunities map to Zoho CRM Deals. The Opportunity's stage maps to Zoho StageName using a customer-approved mapping table created during scoping. Pipeline name in Metis maps to Zoho's Deal Name prefix or a custom field if the customer uses Zoho multiple pipelines. Deal value, close date, and pipeline association migrate directly. The Opportunity's linked Client resolves to the Zoho Account lookup on the Deal.

Metis Jobs represent active project records and map to Zoho Tasks with project metadata fields. For customers who require full project management features (milestones, sub-tasks, time logs), we recommend Zoho Projects as a parallel destination module and migrate Jobs there instead. Job status (active, completed, archived) maps to Zoho Task Status. Job costing fields migrate to custom numeric fields on the Task. Jobs without a linked Client in Metis are flagged as unassigned and held for manual review.

Metis Timesheet entries map to Zoho Tasks with custom time-logging fields. Each timesheet row becomes a separate Task record. Billable vs non-billable flags from Metis map to a custom picklist field on the Zoho Task. Entries with a linked Job become Tasks linked to the parent Job-Task in Zoho. Entries without a Job association are flagged as orphan time entries and presented to the customer for resolution: assign to a default project, skip, or create placeholder jobs.

Metis People Expenses map to a Zoho custom Expenses module or to Zoho Books if the customer licenses it. Expense category, amount, date, and vendor from the People Expenses CSV map directly. Receipt images are stored as separate files outside the CSV export and are transferred in a parallel file operation, with each expense record in the migration log tagged with an image-reattachment note. Customers must verify receipt attachments post-migration in the destination system.

Metis Central Expenses (agency-level overhead) map to the same Zoho custom Expenses module as People Expenses. We distinguish between People-level and Central-level expenses using an expense_type custom field. Receipt images follow the same parallel file transfer process as People Expenses. Central Expenses that should represent vendor bills in an accounting system are flagged for Zoho Books import rather than CRM-only migration.

Metis People records with a user role (those who have login access to Metis) map to Zoho CRM User records. We resolve by matching the Metis user email to the Zoho User email address. Any Metis user without a matching Zoho User is placed in a reconciliation queue for the customer's admin to provision before record import resumes.

Metis Resourcing Reports are filtered views combining People availability with Job assignments, not transactional records. We do not migrate Resourcing Reports as a data object. We extract the underlying Job-People assignment data from the Jobs zone and reconstruct the utilization view as Zoho custom fields on Task and a saved search in Zoho Reports. The customer rebuilds the resourcing dashboard natively in Zoho.

The Xero-friendly People Expenses export is a destination-format variant designed for direct Xero import, not a source object. We do not use this format as the migration source. We extract the standard People Expenses CSV and handle any Xero mapping as a separate destination-side transformation step. If the customer uses Zoho Books instead of Xero, the expense data maps to Zoho Books invoices via the API.