Migrate from Metis CRM to Microsoft Dynamics 365 Sales

Discovery and zone export extraction

We audit the source Metis CRM account across all available zones (Clients, Opportunities, Jobs, People, Timesheets, People Expenses, Central Expenses) and extract the full CSV for each zone. We identify record counts, identify any Metis custom fields per zone, flag the receipt image file locations, and assess the resourcing report data volume. We pair this with a Dynamics 365 environment audit: identifying the target org, confirming Dataverse custom entity provisioning authority, and identifying any existing validation rules or security profiles that will affect import.

Schema design and Dataverse custom entity provisioning

We design the destination schema in Dynamics 365. This includes creating the custom Job entity (with fields mapped from Metis Jobs including job costing, status, and dates), the custom Time Entry entity (with billable/non-billable flags and Person and Job lookups), and the custom Expense entities (for People Expenses and Central Expenses with category, amount, date, and receipt attachment). Schema is deployed into the target environment before any data import. We document any Metis fields that cannot map directly to a Dynamics 365 field and present the customer with custom field options.

Parent-record lookup resolution and orphan audit

We resolve cross-record references across the Metis CSV exports before any Dynamics 365 import. This means matching every Opportunity's Client reference to the Account record being created, matching every Job's Client reference to the Account, matching every Person to a Contact record, and resolving the People and Job references on each Timesheet entry. Orphan records (People without a Client, Timesheet entries without a Job, Expenses without a Person) are flagged in the pre-migration audit and presented to the customer for a disposition decision before production migration begins.

Sandbox migration and reconciliation

We run a full migration into a Dynamics 365 Sandbox environment using production-like data volume. The customer's Dynamics 365 admin reconciles record counts (Accounts in, Contacts in, Opportunities in, custom entity records in), spot-checks 25-50 random records against the Metis source CSV exports, and validates that the receipt image file names correspond to the correct expense records. The customer signs off the schema and mapping before production migration begins. Any mapping corrections happen in the sandbox phase, not in production.

Production migration in dependency order

We run production migration in record-dependency order: Accounts (from Metis Clients), Contacts (with accountid resolved from the Client mapping), Opportunities (with accountid and owninguser resolved), custom Job entity records (with accountid resolved), custom Time Entry records (with person and Job references resolved, orphan entries held pending disposition), custom Expense records (with receipt image reattachment notes logged). Receipt images are transferred in parallel as a separate file batch. Each phase emits a row-count reconciliation report before the next phase begins.

Cutover, validation, and rebuild handoff

We freeze Metis zone exports at cutover and run a final delta export of any records modified during the migration window. We validate the Dynamics 365 production environment and deliver the resourcing report reconstruction file, the orphan time entry disposition log, and the receipt image reattachment checklist. We do not rebuild Metis automations as Dynamics 365 workflows; those are delivered as a written inventory for the customer's admin team. We support a one-week hypercare window where we resolve reconciliation issues raised by the customer's team.