Migrate from Metis CRM to Salesforce Sales Cloud

Metis Client records map directly to Salesforce Account. The client name becomes Account Name, primary contact details map to the Account's standard contact fields, and client status maps to an Account Status custom picklist. We extract the Clients zone CSV as the first migration step because Account is the parent of Contact and the lookup target for Opportunity (WhatId) and any custom Job object. Clients with multiple primary contacts generate an Account with multiple Contact records via the People zone mapping.

Metis People records map to Salesforce Contact. First name, last name, email, phone, role, and address fields transfer directly. The parent Client ID from Metis resolves to an Account ID in Salesforce during import so that every Contact has an Account lookup. People records are extracted from the People zone CSV as the second migration step after Accounts are confirmed in Salesforce.

Metis Opportunity records map to Salesforce Opportunity. The pipeline stage value, estimated value, probability, and close date transfer to Opportunity StageName, Amount, Probability, and CloseDate. The parent Client lookup resolves to the Account ID. We configure a Salesforce Record Type and Sales Process that matches the Metis pipeline structure before migration begins so that stage values are whitelisted at import time.

Metis Jobs are project records with client association, status, dates, and costing fields. Salesforce has no native project object in Sales Cloud, so we configure this mapping in one of two ways during scoping: Jobs become Opportunities with a Project record type (preferred for sales-cycle-adjacent project tracking), or Jobs become a custom Project__c object with an Account lookup and Opportunity lookup (preferred for agency and professional services teams that need job costing separate from pipeline forecasting). The customer selects the strategy before migration. Job costing fields map to custom numeric fields on the destination object.

Metis Timesheets export from the Manage zone as a structured grid with person association, date, hours, billable/non-billable flags, and optional Job linkage. For billable time tied to a Job, we map to a custom Time_Entry__c object linked to the Project (Job) and Contact (Person). Non-billable or general logged time maps to Salesforce Task with ActivityDate set to the timesheet entry date. Orphan time entries — timesheet rows with no Job association — are flagged in the pre-migration audit and presented to the customer with three options: assign to a default project, skip, or create placeholder Jobs for them.

Metis People Expenses export from the Manage zone with expense category, amount, date, and person association. The receipt image is stored as a separate file outside the CSV. We map expense records to a custom Expense__c object with Amount, Date, Category, and Contact lookup. Receipt images transfer via parallel file transfer and re-attach as ContentDocumentLink records linked to the corresponding Expense__c record. Each expense record is flagged in the migration log with an image-reattachment confirmation note for the customer's post-migration review.

Metis Central Expenses are agency-level overhead costs exported from the Manage zone separately from People Expenses. Receipt images are also stored as separate files. We map Central Expenses to a second custom Expense__c variant (expense_type = 'Central') with no Contact lookup, linked to the Account or a custom Agency_Overhead__c object. Receipt re-attachment follows the same parallel file transfer and ContentDocumentLink pattern as People Expenses.

Metis Resourcing reports are filtered views combining People availability with Job assignments — they are not transactional objects. We extract the underlying source data (People zone for availability, Jobs zone for assignments) and construct a custom Resource_Allocation__c object in Salesforce with fields for Person (Contact), Project (Job), start date, end date, and utilization percentage. Utilization percentage is computed from the source data and stored as a custom field.

Metis People with a user-facing role map to Salesforce User by email match. We extract all distinct Metis users referenced on Opportunities, Jobs, and Timesheets and match them against the Salesforce User table by email address. Any Metis user without a matching Salesforce User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Metis allows multiple People records linked to a single Client. After mapping People to Contacts and Clients to Accounts, we create AccountContactRelation records for each Person-Client link to represent the full contact hierarchy in Salesforce. The primary contact flag from Metis maps to the IsPrimary field on AccountContactRelation.

Metis Job status values (Active, On Hold, Completed, Cancelled) map to a custom status picklist on the Project record type or Opportunity stage if Jobs are mapped to Opportunities. We configure the picklist values before migration so that imported Jobs land in the correct status without triggering validation rule rejections.

Each Metis pipeline and its stages map to a Salesforce Sales Process and corresponding StageName values on Opportunity. Stage probabilities transfer from Metis to Salesforce StageProbability, rounded to the nearest integer. We deploy the stage configuration to a Sandbox org first for validation before production migration.