Migrate from Metis CRM to HighLevel

Metis Client records map to GoHighLevel Company records as the primary parent. Each Client's primary contact person maps to a GoHighLevel Contact record linked to that Company. We extract contact-level fields (email, phone, role) from the Client zone and create the Contact record alongside the Company import. The Client name becomes the Company name; the Client's associated People records are linked via the Contact relationship.

Metis People records map directly to GoHighLevel Contact records. We extract all person-level fields from the People zone including role, contact details, and related client associations. Email address is used as the dedupe key during import. Any People records that are the primary contact on a Client are already handled in the Client-to-Company split above and are deduplicated to a single Contact record.

Metis Opportunities map to GoHighLevel Opportunities with pipeline stages, deal value, and client association preserved. The Opportunity stage in Metis maps to the corresponding GoHighLevel pipeline stage name. We configure the GoHighLevel pipeline with matching stage names before migration so that deal status transfers without manual reassignment. The client association links the Opportunity to the mapped Company record.

Metis Jobs represent project records with status, dates, client association, and job costing fields. There is no native project object in GoHighLevel, so we offer two migration paths during scoping: Option A maps active Jobs to Opportunities using Opportunity custom fields (job_status, job_start_date, job_end_date, job_cost) added before import; Option B creates a GoHighLevel Custom Object called Projects with lookup relationships to the associated Company and Opportunity. The customer's choice depends on whether they want job data surfaced in the pipeline view or managed as a separate project layer.

Metis Timesheets map to GoHighLevel Tasks with billable/non-billable flags preserved as custom Task fields. We extract time entries with person association, date, duration, and linked Job. Timesheets without a linked Job (orphan entries) are flagged in the pre-migration audit and presented to the customer with three choices: assign to a placeholder project, skip, or create placeholder Jobs as Custom Objects for time entry association. All retained time entries are imported as Tasks linked to the relevant Contact record.

Metis People Expenses map to a GoHighLevel Custom Object called Expenses with fields for category, amount, date, person association, and receipt reference. Receipt images are exported from Metis as separate files and transferred in parallel to GoHighLevel's file storage. We flag each expense record in the migration log with a receipt-reattachment note indicating the original filename; the customer manually links receipt images in GoHighLevel post-migration.

Metis Central Expenses (agency-level overhead costs) map to the same GoHighLevel Custom Object (Expenses) as People Expenses, distinguished by an expense_type field set to 'Central'. Receipt image handling follows the same parallel file transfer process as People Expenses. Both expense types share the same GoHighLevel custom object schema to preserve category reporting across the migrated dataset.

This Metis export format reformats People Expenses into Xero-compatible schema and is a destination-side format, not a source object. We do not use this format as our migration source. We extract the standard People Expenses CSV and handle any Xero mapping as a separate destination-side transformation step if the customer continues using Xero for accounting. The Xero-friendly export is excluded from the migration scope.