How long does a Metis CRM to Nutshell migration take?

Most migrations land between two and four weeks for accounts under 5,000 total records with straightforward field mapping. Migrations with large Jobs zones requiring Deal remapping, orphan time entry resolution, or Central Expenses mapped to custom fields extend to four to eight weeks. Metis has no API, so the migration is bounded by CSV export preparation time and manual export steps rather than API rate limits. Nutshell's API handles insertion efficiently once the CSV ingestion pipeline is running.

Do Metis Workflows, Resourcing Reports, and Quote templates migrate to Nutshell?

No. Metis Workflows are a platform-specific automation model that does not have a direct Nutshell equivalent. Nutshell's automation capabilities are more limited and focused on pipeline rules rather than multi-step workflow triggers. We deliver a written inventory of every active Metis automation, Resourcing Report configuration, and Quote template with the customer's data populated as a reference document for manual rebuild. Resourcing Reports specifically are view exports, not transactional objects — the underlying People and Job data migrates, but the utilization view does not.

What does a Metis CRM to Nutshell migration typically cost?

Migrations under 5,000 total records with 1:1 field mapping land between $3,500 and $5,500 and complete in two to four weeks. Migrations with Jobs remapping to Deals, orphan time entry resolution, parallel receipt file transfers, or custom field-heavy expense mapping move to $6,500-$9,500 and four to eight weeks. Nutshell subscription costs ($16-$67 per user per month on annual billing) sit outside the migration fee. Metis CRM publishes no public pricing, so the destination cost comparison is based on Nutshell's published tiers.

How do receipt images and expense attachments migrate?

Metis exports receipt images as separate files outside the main CSV, so the expense record migrates but the image does not embed automatically. We run a parallel file transfer for all receipt images and flag each expense record with a re-attachment note. After the migration, the customer reviews flagged expense records in Nutshell and manually attaches the corresponding receipt files via Nutshell's file attachment API. We provide a mapping spreadsheet linking each expense record to its receipt file for efficient re-attachment.

What happens to Metis Jobs (project records) in Nutshell?

Metis Jobs have no direct Nutshell equivalent because Nutshell does not include project management. We map Jobs to Nutshell Deals with custom fields for project status, start date, end date, and costing. The linked Client becomes the Deal's Account. If the customer's Nutshell plan is Pro or Enterprise, we can create a custom Project object with a lookup to Company and custom fields for job costing instead. The customer chooses the strategy during scoping, and Nutshell's deal pipeline view provides a basic project-status overview using the custom fields.

Can we migrate Metis Timesheets to Nutshell?

Yes, but as Task records rather than a native timesheet object. Each Metis timesheet entry becomes a Nutshell Task with the original time note, duration as a custom numeric field, and billable flag as a custom checkbox field. Timesheet entries linked to a Job map to the corresponding Deal created from that Job. Orphan timesheet entries without a Job link are flagged in the pre-migration audit and routed per the customer's chosen strategy: default project, Person-level custom field, or exclusion.

Do we lose data migrating from Metis because there is no API?

No record data is lost from the CSV exports. Metis's per-zone exports capture all records in each zone, including all standard fields. The limitation is that the export is a point-in-time snapshot, so any records created in Metis between the export and the cutover date require a delta export and import. We plan for this in the cutover approach. Receipt images are the one data category that requires a separate parallel file transfer because they are not embedded in the CSV. We manage that transfer and flag records for re-attachment post-migration.

Can FlitStack AI migrate Metis to a CRM other than Nutshell?

Yes. The CSV-based extraction approach we use for Metis is platform-agnostic — the zone exports are standard CSV files that we can transform and insert into any destination CRM with a documented API or import tool. Nutshell is a natural fit because its REST API and Import2 integration provide clean insertion paths, but we have migrated Metis data to HubSpot, Pipedrive, Zoho CRM, and other platforms using the same CSV ingestion pipeline with destination-specific transformation logic.

Metis CRM to Nutshell Migration — Field-Level Mapping & Rollback

Overview

What this migration involves

Moving from Metis CRM to Nutshell is a structural migration from a client-centric, project-management-adjacent platform to a focused sales CRM. Metis organizes data around Clients, Opportunities, Jobs, People, Timesheets, and Expenses; Nutshell uses Companies, People, Deals, and Activities. Metis has no documented public API, so all extraction runs through its per-zone CSV export, which captures records but not embedded attachments. We sequence the migration by parent-first dependency (Clients before Opportunities, People before any linked records), run a parallel file transfer for receipt images, and insert into Nutshell via its REST API. Jobs (Metis project records) have no direct Nutshell equivalent, so we map them to Deals with the client as the Account and a custom project-status field. Timesheets migrate as Task records with the original time entry data preserved as note text. We do not migrate Metis Resourcing Reports because they are view exports, not transactional objects. Workflows, automations, and quote generation in Metis do not migrate; we deliver a written inventory for the customer's admin to rebuild in Nutshell.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Metis CRM

What's pushing teams away

Teams outgrow the platform when they need deeper marketing automation, advanced multi-pipeline reporting, or CRM features beyond basic sales pipeline management.
Lack of a documented public API limits integration options, forcing teams to manual exports or workarounds that become unsustainable at scale.
Project-heavy teams report that job costing and resourcing features are functional but lack the depth of dedicated project management tools.
Small teams report that pricing for multiple users adds up, especially when the feature set overlaps with cheaper standalone tools for specific use cases like time tracking.

Choosing

Nutshell

What's pulling them in

Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How Metis CRM objects map to Nutshell

Each row shows how a Metis CRM object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

Metis CRM

Clients

maps to

Nutshell

Company

1:1

Fully supported

Metis Client records map directly to Nutshell Company records. Client name, address, phone, website, and contact email fields map to the equivalent Nutshell Company fields. The Client record is the primary parent object, so we migrate Companies first before any child records (Opportunities, People) to satisfy the required Account lookup in Nutshell.

Metis CRM

Opportunities

maps to

Nutshell

Deal

1:1

Fully supported

Metis Opportunity records map to Nutshell Deal records. The opportunity stage, value, and close date map to Nutshell's deal stage, monetary value, and expected close date. Client association on the Metis Opportunity resolves to the Nutshell Company lookup. If the Metis Opportunity references a pipeline not present in Nutshell, we create a matching deal stage before migration.

Metis CRM

People

maps to

Nutshell

Person

1:1

Fully supported

Metis People records map to Nutshell Person records. All person-level fields including name, email, phone, role, and associated Company link migrate directly. If a Metis People record has a linked Client, we resolve the Nutshell Company lookup before Person insertion.

Metis CRM

Jobs

maps to

Nutshell

Deal (with custom fields)

1:many

Fully supported

Metis Jobs have no direct Nutshell equivalent because Nutshell does not include project management. We map each Job to a Nutshell Deal with the linked Client as the Account, and we create custom fields on the Deal for job status (Active, Completed, On Hold), job start date, and job end date. Job costing fields (budget, actual cost) migrate as custom monetary fields. This is a common pattern for teams migrating from project-capable CRMs to Nutshell.

Metis CRM

Timesheets

maps to

Nutshell

Task

1:1

Mapping required

Metis Timesheet entries migrate as Nutshell Task records. The task description carries the original time entry note, and the billable flag from Metis maps to a custom task field. Duration in hours migrates as a numeric custom field. For timesheets linked to a specific Job, we map the task to the Deal created from the Job and link the Person record. Orphan time entries without a Job association are flagged in the pre-migration audit and presented to the customer for manual assignment or default-project routing.

Metis CRM

People Expenses

maps to

Nutshell

Deal Line Item (or custom fields)

lossy

Mapping required

Metis People Expenses have no direct Nutshell equivalent. We map expense category, amount, date, and vendor to custom fields on the related Deal (if linked to a Job) or as standalone custom fields on the Person record. The customer chooses the strategy during scoping. Receipt image files are not embedded in the Metis CSV export, so we run a parallel file transfer and flag each expense record with a re-attachment note for manual verification post-migration.

Metis CRM

Central Expenses

maps to

Nutshell

Custom Fields on Company

lossy

Mapping required

Metis Central Expenses are agency-level overhead costs with no direct Nutshell equivalent. We map expense category and amount to custom fields on the related Company record or as a separate custom object if the customer's Nutshell plan supports it. Receipt images for Central Expenses are handled via the same parallel file transfer as People Expenses. The customer reviews and reattaches receipts in Nutshell post-migration.

Metis CRM

Resourcing Report

maps to

Nutshell

Not migrated

1:1

Mapping required

Metis Resourcing Reports are view exports combining People availability with Job assignments, not transactional objects. The underlying data (People, Jobs, and their associations) has already migrated through the Jobs and People mappings. We do not migrate the report view itself; we document its structure and recommend that the customer rebuilds utilization reporting using Nutshell's Deals with custom date and assignment fields, or an external BI tool connected to Nutshell's API.

Metis CRM	Nutshell	Compatibility
Clients	Company1:1	Fully supported
Opportunities	Deal1:1	Fully supported
People	Person1:1	Fully supported
Jobs	Deal (with custom fields)1:many	Fully supported
Timesheets	Task1:1	Mapping required
People Expenses	Deal Line Item (or custom fields)lossy	Mapping required
Central Expenses	Custom Fields on Companylossy	Mapping required
Resourcing Report	Not migrated1:1	Mapping required

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

Metis CRM gotchas

High

No public API forces CSV-only migration paths

Medium

Receipt images exported as separate files outside the main CSV

Medium

Orphan time entries without a linked Job

Low

Xero-friendly export is a destination format, not a source object

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Metis CRM gotchas		Nutshell gotchas
Severity	Issue	Severity	Issue
High	No public API forces CSV-only migration paths	High	Contact tier limits enforced on import
Medium	Receipt images exported as separate files outside the main CSV	Medium	No bulk API endpoint requires paginated extraction
Medium	Orphan time entries without a linked Job	Medium	Email sequences not exportable via API
Low	Xero-friendly export is a destination format, not a source object	Medium	Foundation plan disables key sales features

Pair-specific challenges

Metis has no public API — extraction is CSV-only

Metis CRM does not publish a REST API, so all data extraction runs through the per-zone CSV export function in the help center. We download each zone export (Clients, Opportunities, Jobs, People, Timesheets, Expenses) as a separate file and ingest them in dependency order. Migration speed is bounded by export chunk sizes and manual export steps. We cannot run real-time sync or delta jobs against the platform, which means any records created in Metis after the export window require a separate delta export and import. Customers must be prepared for a discrete cutover rather than a live-sync migration.
Jobs have no direct Nutshell equivalent

Metis Jobs (project records with costing, client association, and status) do not map to any standard Nutshell object. We resolve this by mapping Jobs to Deals with custom fields for project status, start date, and costing data, but this is a structural adaptation not a native equivalent. Teams that rely heavily on Metis Jobs for project tracking should plan for Nutshell custom field configuration before migration and accept that project-level reporting will differ from the Metis experience. The alternative is to create a Nutshell custom object for Projects, which is available on Pro and Enterprise plans but requires pre-migration setup.
Receipt images export outside the main CSV

Both People Expenses and Central Expenses in Metis store receipt images as linked files rather than embedded data. The CSV export captures the expense record but not the image file. We run a parallel file transfer for all receipt attachments and flag each expense record in the migration log with an image-reattachment note. Customers must manually verify and reattach receipt images in Nutshell post-migration, as Nutshell's file attachment API requires the record to exist first before files can be linked.
Orphan time entries without a linked Job

Timesheet exports from Metis may contain entries logged against a Person but without a Job association. These orphan entries cannot be automatically mapped to a project in Nutshell without a Job-to-Deal parent. We flag every unlinked time entry in the pre-migration audit and present the customer with a mapping choice: assign to a default placeholder Deal, link to the Person record with a custom time field, or skip the entry. The choice depends on whether the orphaned time data is business-critical or can be safely excluded from the migration.

Migration approach

Six steps for a successful Metis CRM to Nutshell data migration

Discovery and zone export preparation

We audit the Metis account across all zones (Clients, Opportunities, Jobs, People, Timesheets, People Expenses, Central Expenses) to establish record counts, field inventory, and dependency relationships. We map each Metis zone to its Nutshell destination object and confirm the custom field configuration plan for Jobs, Timesheets, and Expenses. We identify orphan time entries (Timesheet rows without a Job link) and present the routing options to the customer. We also confirm the Nutshell plan tier to verify custom field limits before migration.
CSV zone export and parallel file extraction

We guide the customer through downloading each Metis zone export as a CSV file: Clients zone, Opportunities zone, Jobs zone, People zone, Timesheet report, People Expenses report, and Central Expenses report. Receipt images are extracted as a separate file batch from the Manage zone. All files are uploaded to a secure FlitStack AI staging environment. We validate the CSV structure against the zone's documented field list and flag any columns that appear empty or inconsistent across rows.
Data profiling and orphan resolution

We run a data profiling pass across all CSV imports to identify duplicates (same client name, same person email), missing required fields, and orphan time entries. Duplicate clients are reconciled using domain and name matching with the customer's input on which record is master. Orphan time entries are collected into a resolution list with the customer's chosen routing strategy applied before migration. Expenses are profiled for category consistency to support custom field mapping.
Nutshell custom field and stage configuration

Before any data insertion, we configure Nutshell custom fields for Job status, job costing, timesheet duration, expense category, expense amount, and billable flags. We also configure Nutshell deal stages to match the Metis opportunity stages, creating any missing stages in Nutshell before migration. If the customer has a Nutshell Pro or Enterprise plan, we offer to create a custom Project object as an alternative to Job-as-Deal mapping.
Migration execution in dependency order

We insert data into Nutshell via its REST API in parent-first order: Companies (from Metis Clients), then People (with Company lookup resolved), then Deals (from Metis Opportunities with stage mapping), then Deals from Jobs (with custom fields populated), then Tasks (from Timesheets with orphan routing applied), then custom field values on Deals and People (from Expenses with parallel file transfer for receipts). Each phase emits a row-count reconciliation report. The parallel receipt file transfer runs concurrently with record insertion so that files are ready to attach once the target records exist in Nutshell.
Cutover, validation, and inventory handoff

We freeze writes to Metis during the cutover window, run a final delta export for any records created or modified after the initial export, and insert the delta into Nutshell. We validate 25-50 records per object against the source CSVs and confirm record counts match. We deliver a written inventory of all Metis automations, quote templates, and Resourcing Report configurations requiring manual rebuild in Nutshell. We support a three-day post-migration window for reconciliation issues raised by the customer team.

Platform deep dives

Context on both ends of the pair

Metis CRM

Source

Strengths

Unified CRM, project management, and time tracking for professional services workflows
Per-zone CSV export capability gives clean data extraction points for migration
Client-centric data model with Opportunities, Jobs, People, and Timesheets as first-class objects
Resource management and resourcing reports for tracking team utilization across jobs
Affordable positioning for freelancers, agencies, and SMBs without enterprise overhead

Weaknesses

No documented public REST API — all migrations rely on CSV zone exports
No clear pricing page or published tier structure in available sources
Receipt images and attachments stored as separate files outside the primary data export
Resourcing reports are view exports, not transactional objects — underlying data must be reconstructed
Limited integrations compared to established CRM platforms

Nutshell

Destination

Strengths

Simple, intuitive interface with minimal learning curve for sales teams new to CRM
Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
Full data export tool available for all account data including backups
Open JSON-RPC API allows programmatic access to all core objects
Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

	Metis CRM Source	Nutshell Destination
Strengths	Unified CRM, project management, and time tracking for professional services workflows Per-zone CSV export capability gives clean data extraction points for migration Client-centric data model with Opportunities, Jobs, People, and Timesheets as first-class objects Resource management and resourcing reports for tracking team utilization across jobs Affordable positioning for freelancers, agencies, and SMBs without enterprise overhead	Simple, intuitive interface with minimal learning curve for sales teams new to CRM Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost Full data export tool available for all account data including backups Open JSON-RPC API allows programmatic access to all core objects Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication
Weaknesses	No documented public REST API — all migrations rely on CSV zone exports No clear pricing page or published tier structure in available sources Receipt images and attachments stored as separate files outside the primary data export Resourcing reports are view exports, not transactional objects — underlying data must be reconstructed Limited integrations compared to established CRM platforms	Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Metis CRM and Nutshell.

Object compatibility
B
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
C
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
B
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
B
Metis CRM: Not publicly documented.
Data volume sensitivity
B
Metis CRM doesn't expose a bulk API — REST + parallelization used for high-volume runs.

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

Migrate from Metis CRM to Nutshell

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

Metis CRM

Nutshell

How Metis CRM objects map to Nutshell

What specifically takes care here

Six steps for a successful Metis CRM to Nutshell data migration

Context on both ends of the pair

How hard is this migration?

Estimate your Metis CRM to Nutshell migration cost

What are you migrating?

Frequently asked questions about Metis CRM to Nutshell data migrations

Can't find your answer?

Related migrations to explore

Move from Metis CRM.
Land in Nutshell, intact.

Migrate from Metis CRM to Nutshell

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

Metis CRM

Nutshell

How Metis CRM objects map to Nutshell

What specifically takes care here

Six steps for a successful Metis CRM to Nutshell data migration

Context on both ends of the pair

How hard is this migration?

Estimate your Metis CRM to Nutshell migration cost

Frequently asked questions about Metis CRM to Nutshell data migrations

Can't find your answer?

How long does a Metis CRM to Nutshell migration take?

Do Metis Workflows, Resourcing Reports, and Quote templates migrate to Nutshell?

What does a Metis CRM to Nutshell migration typically cost?

How do receipt images and expense attachments migrate?

What happens to Metis Jobs (project records) in Nutshell?

Can we migrate Metis Timesheets to Nutshell?

Do we lose data migrating from Metis because there is no API?

Can FlitStack AI migrate Metis to a CRM other than Nutshell?

Related migrations to explore

Move from Metis CRM. Land in Nutshell, intact.

Move from Metis CRM.
Land in Nutshell, intact.