Migrate from Metis CRM to Freshsales

Metis Clients map to Freshsales Account. The client name becomes Account Name, contact email becomes the primary contact email, and address fields map to the standard Account address fields. Account is created before any Contact import so that the Account-Contact relationship is satisfied at the moment of Contact insert. Metis does not gate Client exports by tier, so all clients extract regardless of the source plan.

Metis Opportunities map to Freshsales Deal. The opportunity stage maps to Freshsales Deal stage, the estimated value maps to Deal Amount, and the pipeline association maps to a Freshsales pipeline that we configure before migration. Closed-Lost and Closed-Won status from Metis map to Freshsales Deal status with the original stage preserved for reporting continuity.

Metis Jobs represent project records and map to Freshsales Deal with a set of custom fields capturing the job-specific data: job status, start and end dates, client association (AccountId lookup), and any job costing fields. We create the custom fields in Freshsales during schema setup, then populate them during the Deal import. Jobs that are billable but not yet opportunity-qualified are imported as Deals with a custom field job_type__c = 'project' to distinguish from standard sales pipeline entries.

Metis People records map to Freshsales Contact. Each Person's role, contact details, and associated client link to the corresponding Account. If the customer uses Metis for unqualified prospect tracking alongside Clients, we apply a Lead-Contact split rule during scoping: people records without an Opportunity or Job association are imported as Freshsales Leads; those with an Opportunity or Job are imported as Contacts under the related Account. The customer defines the split rule before migration begins.

Metis Timesheets map to Freshsales Task records representing logged time. Each Task records the date, duration (hours or minutes mapped to Task.ActivityDate and a custom duration field), billable flag, and Job association if present. We flag time entries without a linked Job as orphan entries in the pre-migration audit and present the customer with a mapping choice: assign to a default project Task, skip, or create placeholder Jobs for them before migration resumes.

Metis People Expenses map to Freshsales Notes or Cases depending on whether the customer wants expense tracking as a support-style log or as linked notes on the Account. Receipt images are exported separately from the expense CSV and transferred as a parallel file operation. Each expense record in the migration log is flagged with an image-reattachment note directing the customer to reattach the receipt file in Freshsales after migration. Expense category maps to a custom picklist field.

Metis Central Expenses (agency-level overhead costs) export separately from People Expenses and map to the same destination objects as People Expenses. We treat Central Expenses as Notes or Cases on the Account level rather than tied to a specific Contact. Receipt images for Central Expenses follow the same parallel file transfer and reattachment workflow as People Expenses.

Metis Owners referenced on Clients, Opportunities, Jobs, and People are resolved by email match against Freshsales User records. We extract every distinct Owner email and attempt to match it to an existing Freshsales User. Any Owner without a matching User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Active Users receive their assigned records; inactive or missing Users receive a placeholder assignment that the admin updates post-migration.