How long does a TeamWave to Nutshell migration take?

Most migrations land between two and three weeks for accounts under 5,000 Contacts and 2,000 Deals where the data extracts cleanly via CSV. Migrations with large batched CSV exports, complex Project-to-Company remapping, HR record translation, or historical Activity records move to four to six weeks because of the multi-phase extract, merge, and validation work required before any Nutshell API calls begin.

Do TeamWave Projects, Tasks, and HR records migrate to Nutshell?

Projects and Tasks have no direct Nutshell object. We map Projects to custom fields on the linked Company record and Tasks to Nutshell Activities with project metadata preserved in a custom text field. HR records map to Nutshell People with Role and Department custom fields. This is a known limitation of the TeamWave-to-Nutshell pair: the project-task hierarchy is flattened and the HR module does not migrate as a standalone object. We document the full source list in the migration manifest for the customer's admin to validate and restructure if needed.

What does a TeamWave to Nutshell migration typically cost?

Migrations under 5,000 Contacts, 2,000 Deals, and no complex Project or HR remapping land between $1,500 and $2,500. Migrations with large CSV batch exports, Project-to-Company custom field remapping, HR record translation, or Activity history move to $3,000-$4,500. Nutshell subscription (starting at $19/user/month) sits outside the migration fee. TeamWave Pro ($30/month flat) is advisory-only for export scoping; it is not a FlitStack AI cost.

Do TeamWave workflows, automations, or project task dependencies migrate to Nutshell?

No. TeamWave workflows and automations are platform-specific automation constructs that do not have a direct Nutshell equivalent. Project task dependencies (parent-child task hierarchies, milestone relationships) do not migrate because Nutshell has no native Project object. We deliver a written inventory of every active TeamWave automation and project workflow for the customer's admin to review and rebuild in Nutshell using Nutshell's workflow automation features or a third-party project management tool. This inventory is included in the migration manifest at no additional cost.

Can file attachments from TeamWave be migrated to Nutshell?

No. TeamWave provides no bulk attachment download mechanism, so we cannot export binary files. We capture attachment metadata (filename, file size, linked object type, and the source record ID) in a re-upload manifest CSV. The customer's admin uses this manifest to manually re-upload each file to the corresponding Nutshell record after migration. We do not charge for this manifest delivery; it is part of the standard scope. The re-upload step is the customer's responsibility.

Why do we need to create custom fields in Nutshell before migration?

Nutshell requires custom fields to be created in the admin settings before any data import populates them. Since TeamWave supports custom fields on Contacts, Deals, Projects, and Tasks, and Nutshell supports custom fields on People, Companies, and Leads, we map TeamWave's custom fields to the appropriate Nutshell object. We provide a manifest listing each source field, its data type, and the recommended Nutshell field configuration. The customer's Nutshell admin creates these fields following our instructions; this takes one to two business days and requires no FlitStack AI involvement beyond the manifest delivery.

How does Nutshell's white glove import service compare to FlitStack AI?

Nutshell's white glove import service is designed for simple, structured CSV imports into a new Nutshell account. It works well for clean contact and company lists without complex relationships or custom field requirements. FlitStack AI handles the full migration scope including relationship resolution (Deal-to-Person lookups, owner assignment, Company-Person linking), multi-object dependency ordering, Activity history import, and Project and HR record translation that exceeds the scope of a standard CSV column mapping. If your TeamWave data is relational with many cross-object references, a structured CSV import without relationship resolution will result in orphaned or unlinked records.

What happens to TeamWave data after migration is complete?

We do not delete or modify TeamWave data. The customer's account remains active until they choose to cancel the subscription directly with TeamWave. We recommend keeping TeamWave read-only for a 30-day validation window after cutover so that the team can reference historical data in Nutshell and request corrections before closing the TeamWave account. We do not provide data deletion or account cancellation services for TeamWave.

TeamWave to Nutshell Migration — Field-Level Mapping & Rollback

Overview

What this migration involves

Moving from TeamWave to Nutshell is a platform reduction from an integrated CRM-Project-HR suite to a focused sales CRM. TeamWave stores CRM data across Contacts, Companies, Deals, Projects, Tasks, Users, and HR records with interrelated foreign keys; Nutshell uses People, Companies, Deals, Leads, Activities, and custom fields on People and Companies. Since TeamWave publishes no public API reference, all extraction relies on CSV exports from the web UI, and we reconstruct record relationships by cross-referencing IDs embedded in the export. Projects and Tasks have no direct Nutshell object, so we map them to custom fields on the linked Company or Deal, flagging this scope for manual validation in Nutshell's admin settings. HR records map to People with a department Role custom field. Attachments do not migrate; we snapshot metadata and hand off a re-upload manifest. Workflows, automations, and project management task dependencies do not migrate as code.

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

TeamWave

What's pushing teams away

Limited advanced customization on workflows, dashboards, and reports forces growing teams to switch to HubSpot, Pipedrive, or Zoho once their process complexity increases.
Reporting lacks deep analytical capabilities; teams that need cohort analysis, attribution, or BI-grade dashboards have to export to spreadsheets or move to a dedicated CRM.
No publicly documented API or developer portal blocks any meaningful integration with marketing automation, finance systems, or custom internal tools.
Thin third-party review corpus (24 reviews on G2, a handful on Capterra) and the vendor's unfunded status since 2015 raise long-term viability concerns for teams making multi-year commitments.
Attachments cannot be exported in bulk and the HR module is light on payroll, time-off accrual, and compliance features compared to BambooHR or Gusto, so teams outgrow it quickly on the people-operations side.

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 TeamWave objects map to Nutshell

Each row shows how a TeamWave 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.

TeamWave

Contact

maps to

Nutshell

Person

1:1

Fully supported

TeamWave Contacts map directly to Nutshell People. We extract the full contact record including name, email, phone, address, and lifecycle stage, then map these to the standard Person fields in Nutshell. Any custom fields on the TeamWave Contact migrate to Nutshell custom fields on People. The company_id foreign key is retained so that each Person can be linked to its corresponding Nutshell Company after the Company import phase completes.

TeamWave

Company

maps to

Nutshell

Company

1:1

Fully supported

TeamWave Company records map 1:1 to Nutshell Companies. The company domain and address fields map directly. Company records are imported before People so that the Company lookup relationship is satisfied at the moment of Person insert.

TeamWave

Deal

maps to

Nutshell

Deal

1:1

Fully supported

TeamWave Deals map to Nutshell Deals with stage, value, owner, and expected close date preserved. The dealstage property maps to the Nutshell pipeline stage, and owner assignment resolves by email match against the Nutshell User table. Note that Nutshell does not support custom fields on Deals, so any custom properties on a TeamWave Deal must be mapped to custom fields on the linked Company or Person, which we flag during scoping.

TeamWave

Project

maps to

Nutshell

Custom fields on Company or Person

lossy

Fully supported

TeamWave Projects have no direct Nutshell equivalent. We map Project name and client association to a custom text field on the linked Company, and project status, start date, and end date to custom date and picklist fields on the same Company record. Customers with multiple Projects per Company store them as newline-delimited or JSON-structured custom field values. This is a known limitation of the mapping; we document the full Project list in the migration manifest for the customer's admin to restructure if needed.

TeamWave

Task

maps to

Nutshell

Activity (Task)

lossy

Fully supported

TeamWave Tasks linked to Projects or Contacts map to Nutshell Activities. We preserve the task subject, status, priority, assignee, due date, and the project_id reference as a custom text field on the Activity for traceability. Task hierarchy and parent-child relationships from TeamWave are flattened into individual Activity records; we document the original hierarchy in the migration manifest.

TeamWave

User / Team Member

maps to

Nutshell

User

1:1

Fully supported

TeamWave Users map to Nutshell Users by email match. Any HubSpot Owner references on Deals and Activities resolve to the corresponding Nutshell User after the User mapping phase. Users without a matching Nutshell account go to a reconciliation queue for the customer's admin to provision before record import resumes.

TeamWave

Calendar Events

maps to

Nutshell

Activity (Task)

1:1

Mapping required

TeamWave Calendar records carrying event title, date/time, linked entity, and attendees migrate to Nutshell Activity records with the event date preserved as ActivityDate. Linked entity resolves to the appropriate Person or Deal lookup in Nutshell.

TeamWave

HR Records / Employees

maps to

Nutshell

Person with custom fields

lossy

Mapping required

TeamWave HR records (name, role, department, basic metadata) map to Nutshell People records with a Role custom field and Department custom field. Since Nutshell has no native HR module, employee records coexist with customer People records; we use a Person type custom field to distinguish employee from customer records during import.

TeamWave	Nutshell	Compatibility
Contact	Person1:1	Fully supported
Company	Company1:1	Fully supported
Deal	Deal1:1	Fully supported
Project	Custom fields on Company or Personlossy	Fully supported
Task	Activity (Task)lossy	Fully supported
User / Team Member	User1:1	Fully supported
Calendar Events	Activity (Task)1:1	Mapping required
HR Records / Employees	Person with custom fieldslossy	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.

TeamWave gotchas

High

No publicly documented API endpoint surface

Medium

Attachment export requires manual re-upload

Medium

Free tier enforces feature caps that affect migration scope

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

TeamWave gotchas		Nutshell gotchas
Severity	Issue	Severity	Issue
High	No publicly documented API endpoint surface	High	Contact tier limits enforced on import
Medium	Attachment export requires manual re-upload	Medium	No bulk API endpoint requires paginated extraction
Medium	Free tier enforces feature caps that affect migration scope	Medium	Email sequences not exportable via API
		Medium	Foundation plan disables key sales features

Pair-specific challenges

No public API requires batched CSV extraction

TeamWave publishes no developer API reference. All data extraction relies on CSV exports from the web UI. If the dataset exceeds the UI's single-export limit, repeated manual exports are required and we merge results by cross-referencing ID columns. We script the UI-based export repetition for large datasets, but datasets over 10,000 records per object take significantly longer to extract and verify than API-based migrations. We advise customers to upgrade to TeamWave Pro before export if they are on the Basic free tier, which enforces feature caps on exports.
Attachments cannot be bulk-exported from TeamWave

TeamWave stores file attachments linked to Contacts, Deals, and Projects but provides no bulk download mechanism. We snapshot attachment metadata (filename, size, linked object type and ID) into a manifest CSV. Binary files must be re-uploaded manually in Nutshell post-migration. We provide a re-upload manifest with the original filename, the destination record type, and the record ID so that the customer's admin can match and re-upload in a systematic review session.
Projects and Tasks have no direct Nutshell object

TeamWave's native Project and Task objects have no equivalent in Nutshell's schema. We map Projects to custom fields on the linked Company record and Tasks to Nutshell Activities with project metadata stored in a custom text field. This means the project-task hierarchy is flattened. Customers with complex project management requirements should plan to evaluate a dedicated project management tool alongside Nutshell post-migration; we do not migrate project dependencies or Gantt data.
Nutshell does not support custom fields on Deals

Nutshell allows custom fields on People, Companies, and Leads, but not on Deals. Any custom properties stored on TeamWave Deals (such as custom deal flags, internal order numbers, or non-standard stage metadata) must map to custom fields on the associated Company or Person record. We flag every custom Deal property during scoping, and the customer chooses the destination field per property. This is a known Nutshell schema limitation that affects any TeamWave-to-Nutshell migration.
Nutshell custom fields require manual creation before import

Nutshell custom fields are created within the Nutshell admin settings before any data import. We provide a custom field manifest listing every TeamWave custom field, its source data type, and the recommended Nutshell field type (Text, Long Text, Currency, Date, Picklist). The customer's Nutshell admin must create these fields before production import begins. We include step-by-step instructions with the manifest. This adds one to two days to the migration timeline if the admin is unfamiliar with Nutshell's settings.

Migration approach

Six steps for a successful TeamWave to Nutshell data migration

Scoping and export preparation

We audit the TeamWave account for record counts across Contacts, Companies, Deals, Projects, Tasks, Users, and HR records. We check the current plan tier and advise upgrading to Pro temporarily if the customer is on the Basic free tier to remove export caps. We outline the full object list, flag every TeamWave custom field, and document the Project-to-Company and Task-to-Activity mapping strategy. The output is a written scope document with a per-object record count estimate.
CSV extraction from TeamWave

We extract data from TeamWave via the web UI in CSV format. For large datasets, we script repeated batch exports and merge results by cross-referencing ID columns and the company_id foreign key. We verify row counts per object against the scoping estimate and flag any missing relationships before proceeding. The merged CSVs become the migration source of truth.
Nutshell custom field creation

We provide the customer with a custom field manifest listing every TeamWave custom field, its source data type, and the recommended Nutshell field type and target object (Person or Company). The customer's Nutshell admin creates these fields in Nutshell settings before import begins. We include step-by-step instructions and screenshots from Nutshell's custom field documentation. This step requires no FlitStack AI involvement beyond delivering the manifest.
Staging migration and reconciliation

We run a test migration into the customer's Nutshell staging environment using a subset of data. We verify record counts (People in, Companies in, Deals in, Activities in), spot-check ten to fifteen records per object against the TeamWave source CSVs, and confirm that custom field values populated correctly. Any mapping corrections are applied before the production migration begins.
Production migration in dependency order

We run production migration in record-dependency order: Nutshell Users (validated), Companies (from TeamWave Companies), People (with Company lookup resolved), Deals (with owner resolved by email match), Activities (Tasks and Events from TeamWave Calendar and Tasks), and HR records (as People with Role and Department custom fields). Projects are written to custom fields on the linked Company record. Each phase emits a row-count reconciliation report before the next phase begins. We use Nutshell's REST API for all writes with rate-limit handling and retry logic.
Attachment manifest delivery and cutover

We deliver the attachment metadata manifest with original filenames, sizes, linked object types, and destination record IDs so the customer's admin can re-upload files in Nutshell. We freeze TeamWave writes during cutover, run a final delta check for any records modified during the migration window, then hand off Nutshell as the system of record. We provide a one-week hypercare window for reconciliation issues. Workflows, project automations, and HR module logic do not migrate and are documented separately for admin review.

Platform deep dives

Context on both ends of the pair

TeamWave

Source

Strengths

Free tier available for basic CRM and task management with no per-user cost
Native mobile apps for iOS and Android alongside a web interface
Unified platform combining CRM, project management, and HR in one subscription
Visual deal pipeline with stage tracking and deal value reporting
Self-described as easy to implement without prior CRM experience

Weaknesses

Small G2 review sample (24 reviews) makes aggregate ratings hard to trust
Unfunded company since 2015 raises questions about long-term support and development
Public API documentation is not publicly accessible or indexed
Limited enterprise-grade features compared to HubSpot, Bitrix24, or monday CRM
India-based team may present timezone and localization gaps for non-Asia customers

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

	TeamWave Source	Nutshell Destination
Strengths	Free tier available for basic CRM and task management with no per-user cost Native mobile apps for iOS and Android alongside a web interface Unified platform combining CRM, project management, and HR in one subscription Visual deal pipeline with stage tracking and deal value reporting Self-described as easy to implement without prior CRM experience	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	Small G2 review sample (24 reviews) makes aggregate ratings hard to trust Unfunded company since 2015 raises questions about long-term support and development Public API documentation is not publicly accessible or indexed Limited enterprise-grade features compared to HubSpot, Bitrix24, or monday CRM India-based team may present timezone and localization gaps for non-Asia customers	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. 2 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 TeamWave and Nutshell.

Object compatibility
B
2 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
TeamWave: Not publicly documented.
Data volume sensitivity
B
TeamWave 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 TeamWave 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

TeamWave

Nutshell

How TeamWave objects map to Nutshell

What specifically takes care here

Six steps for a successful TeamWave to Nutshell data migration

Context on both ends of the pair

How hard is this migration?

Estimate your TeamWave to Nutshell migration cost

What are you migrating?

Frequently asked questions about TeamWave to Nutshell data migrations

Can't find your answer?

Related migrations to explore

Move from TeamWave.
Land in Nutshell, intact.

Migrate from TeamWave 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

TeamWave

Nutshell

How TeamWave objects map to Nutshell

What specifically takes care here

Six steps for a successful TeamWave to Nutshell data migration

Context on both ends of the pair

How hard is this migration?

Estimate your TeamWave to Nutshell migration cost

Frequently asked questions about TeamWave to Nutshell data migrations

Can't find your answer?

How long does a TeamWave to Nutshell migration take?

Do TeamWave Projects, Tasks, and HR records migrate to Nutshell?

What does a TeamWave to Nutshell migration typically cost?

Do TeamWave workflows, automations, or project task dependencies migrate to Nutshell?

Can file attachments from TeamWave be migrated to Nutshell?

Why do we need to create custom fields in Nutshell before migration?

How does Nutshell's white glove import service compare to FlitStack AI?

What happens to TeamWave data after migration is complete?

Related migrations to explore

Move from TeamWave. Land in Nutshell, intact.

Move from TeamWave.
Land in Nutshell, intact.