Migrate from Metis CRM to HubSpot

Metis clients map directly to HubSpot companies. Company name, domain, industry, and address fields translate cleanly. Metis client hierarchies (parent/child) map to HubSpot's parent company association via the parent_company_id field. Multi-client relationships need secondary company associations in HubSpot. During import, we validate that each company record includes a valid domain; any missing domains are flagged for manual entry before the final load.

Metis people map to HubSpot contacts 1:1. First name, last name, email, phone, job title, and address fields translate directly. Each contact is linked to a primary company via the company field. Metis contact roles within opportunities map to HubSpot deal-to-contact associations.

Metis opportunities map to HubSpot deals. Deal name, amount, stage, close date, and owner translate directly. HubSpot deal amount is stored as a number field; Metis currency formatting is stripped during import. The opportunity stage (Lead, Proposal, Won, Lost) maps to a HubSpot deal stage value via value mapping.

Jobs split based on type: project-oriented jobs map to HubSpot deals with custom fields for budget and scope; service/support jobs map to HubSpot tickets with the ticket status reflecting job stage. We surface this split decision in the migration plan before the first record moves.

Job budget and estimated hours migrate as HubSpot deal custom properties (Job_Budget__c, Job_Estimated_Hours__c). Timesheet totals and expense totals also land as custom number fields on the associated deal so financial context is visible without opening the source system. These custom fields are created in HubSpot with the appropriate type (currency for budget, number for hours) and are included in the import template so values map automatically.

Metis opportunity stages (Lead, Proposal, Negotiation, Won, Lost) map to HubSpot deal stages by value. Each stage probability is re-applied from HubSpot's stage settings. If Metis stages don't match HubSpot defaults, we create custom stage values in the target pipeline.

Timesheet data for each job lands as a note on the linked deal record with the original date, hours logged, and user. Aggregated totals (total hours per job) also populate a custom number field for reporting. We preserve the note format for audit continuity.

Metis expense records attach to jobs and carry description, amount, and date. Each expense migrates as a note on the parent deal with amount and date. The total expenses per job populates a custom currency field (Job_Expenses__c) so margin calculations are possible in HubSpot reports.

Metis stores an owner on opportunities and jobs. We match Metis owner email against HubSpot user email to resolve OwnerId. Unmatched owners are flagged before migration — either invited to HubSpot or assigned to a fallback owner. No record lands without an owner assignment.

Any Metis custom fields attached to clients, people, or opportunities require HubSpot custom properties created before import. We deliver a property-creation checklist based on the Metis export field list. Data types are matched: text → string, number → number, date → date, picklist → enumeration.

Metis opportunity reports contain stage history and value changes over time. We preserve this as notes on the HubSpot deal with timestamps and stage names. Activity timeline reflects the historical progression for reporting continuity.

Metis resourcing reports track which people are assigned to which jobs. This N:1 relationship has no direct HubSpot equivalent — we capture the assignment as a custom multi-select text property (Resource_Assignments__c) on the deal for reference, but full resourcing management requires HubSpot's native resource management features or a third-party integration. These assignments are stored as a comma‑separated list for quick reference and reporting.