Migrate from Metis CRM to monday CRM

Metis Client records map directly to Monday.com CRM Company records. The Company name, address, phone, website, and custom fields migrate to Monday.com Company fields. Company is created before any related Person or Opportunity import so that the Monday.com People record's Company association is satisfied at the moment of insert. Clients without a contact person are imported as standalone Company records and flagged in the migration log for manual owner assignment.

Metis Opportunity records map to Monday.com Deals. Stage, value, pipeline association, and close date migrate to the Deal's Status, Amount, and custom date column. The pipeline from Metis maps to a Monday.com board with a Status column that reproduces the original pipeline stages. We preserve the Metis Opportunity value as a custom number column if the Monday.com Deals board does not use the native Amount field.

Metis Job records require a schema design decision. Options are: (a) a single Jobs board with groups per job type, or (b) separate boards per job type for teams with distinct project workflows. The customer's Metis Job type distribution drives the choice. Job costing fields (budget, actual hours, margin) migrate as custom number and formula columns on the board. Jobs are imported after their parent Client so that the Monday.com item carries the correct Client association.

Metis People records map to Monday.com People records with role, contact details, and related client preserved as custom columns. Email, phone, and address migrate to the standard Monday.com People fields. Role and department become custom text or dropdown columns. People records are imported after Companies so that the Company-Person association links correctly. Metis People with no linked Client are imported as standalone People records and flagged for owner assignment.

Monday.com has no native timesheet object. We create a Time Entries board with Person (linked to Monday.com People), Date, Job (linked to the relevant Job board item), Hours, and Billable flag columns. Orphan time entries (Metis timesheet records without a linked Job) are flagged in the pre-migration audit. The customer chooses: assign to a default placeholder Job item, skip the entry, or have FlitStack AI create placeholder Job items for each distinct orphaned project. We do not silently drop orphan entries — the choice is explicit.

Metis People Expenses are expense records tied to a Person. We create an Expenses board with columns for Person, Category, Amount, Date, and Status. Receipt images are not embedded in the CSV export — the image files are transferred in a parallel file operation, and each expense record is flagged in the migration log with a re-attachment note instructing the customer to re-link the image in Monday.com manually. Category mappings from Metis to Monday.com dropdown values are defined during scoping.

Metis Central Expenses are agency-level overhead costs. They migrate to the same Expenses board as People Expenses with a Type column distinguishing between people-level and agency-level costs. Receipt images for Central Expenses follow the same parallel file transfer and re-attachment note process as People Expenses.

Metis Resourcing Reports are filtered views combining People availability with Job assignments, not transactional records. We do not export the view as data because it contains no records not already present in People and Job zones. Instead, we extract the underlying People and Job data and design Monday.com board filtered views that reproduce the availability and allocation perspective from the original Resourcing Report.