CRM migration
Field-level mapping, validation, and rollback between Teamgate and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Teamgate
Source
Nutshell
Destination
Compatibility
8 of 10
objects map 1:1 between Teamgate and Nutshell.
Complexity
BStandard
Timeline
1-3 weeks
Overview
Moving from Teamgate to Nutshell is a migration between two SMB-focused, pipeline-first CRMs with different data models that require deliberate mapping at the Contact-Company link level and the Deal-to-Opportunity stage level. Teamgate treats People and Companies as separate but linked records; Nutshell uses Contacts as the primary record with an optional Company link. We resolve that link during scoping, extract all custom fields from Teamgate's API alongside the standard field schema, and map the pipeline stage structure (including stage order and probability percentages) into Nutshell's pipeline configuration before migration begins. Activity history, tags, and file attachments migrate as separate object types. We do not migrate SmartDialer configurations, integration OAuth tokens, or workflow automation rules as these are source-platform-only settings.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Teamgate 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.
Teamgate
People
Nutshell
Contact
1:1Teamgate People records map directly to Nutshell Contacts. All standard fields (name, email, phone, address, job title) transfer 1:1. Custom fields on People migrate to Nutshell custom fields on Contact, with field type mapping (Teamgate text, number, date, dropdown, checkbox to equivalent Nutshell field types). The Teamgate import history limitation means that records originally imported via CSV into Teamgate show the Teamgate import date rather than the original source timestamp; we document this during extraction and capture any available original timestamps from Teamgate's API if they exist.
Teamgate
Company
Nutshell
Company
1:1Teamgate Company records map directly to Nutshell Company records. Industry classification, address, and custom fields transfer 1:1. Nutshell's Company link on Contact is an optional field that we populate during Contact migration by resolving the Company name or domain on the Teamgate People record against the Teamgate Company records, then linking the Nutshell Contact to the corresponding Nutshell Company record via the link field.
Teamgate
Deal
Nutshell
Opportunity
1:1Teamgate Deals map to Nutshell Opportunities. Deal value, expected close date, loss reason, and owner assignment transfer directly. The Teamgate pipeline stage assignment maps to the corresponding Nutshell pipeline stage via the stage name or order number. Loss reasons export from Teamgate as a custom property and are created as new values in Nutshell's loss reason dropdown during migration setup.
Teamgate
Pipeline
Nutshell
Pipeline
lossyTeamgate's named Pipelines (including stage names, stage order, and probability percentages per stage) are exported in full and recreated in Nutshell's pipeline configuration. Nutshell allows multiple pipelines with custom stage names and probabilities. We map each Teamgate pipeline to a distinct Nutshell pipeline, preserving stage order and win/loss probability values as close to the source percentages as Nutshell's configuration allows.
Teamgate
Pipeline Stages
Nutshell
Pipeline Stages
lossyEach stage within a Teamgate Pipeline maps to a corresponding stage in the Nutshell pipeline. Stage sequence order and probability percentages migrate. Nutshell's stage editor allows reordering and probability assignment per stage. If the customer has multiple Teamgate pipelines with different stage sets, each pipeline is recreated independently in Nutshell with its own stage configuration.
Teamgate
Custom Fields
Nutshell
Custom Fields
1:1Teamgate custom fields on People, Companies, and Deals are exported as a schema alongside their data. We create equivalent custom fields in Nutshell before migration begins, matching the field type (text, number, date, dropdown, checkbox). Dropdown values in Teamgate map to Nutshell's dropdown option lists. The field order and placement on the record layout is documented in the mapping output.
Teamgate
Tags
Nutshell
Tags
1:1Teamgate's flat tag strings on People, Companies, and Deals export as normalized lists per record. Nutshell stores tags as a multi-select field on Contacts and Companies. We export the full tag vocabulary from Teamgate, create corresponding tag values in Nutshell's tag field, and map each record's tag list to the Nutshell multi-select field. Tags that do not yet exist in Nutshell are created during migration setup.
Teamgate
Activities (Tasks, Calls, Emails, Meetings)
Nutshell
Activities
1:1Teamgate activity records (tasks, calls, emails, meetings with type, timestamp, duration, and notes) attach to People or Deals. Nutshell records activities on the Contact timeline. We map Teamgate activity types to Nutshell activity types (call, email, meeting, task, note), preserving the original timestamp and activity content. Activity owner assignment resolves via the Teamgate owner email to the corresponding Nutshell user.
Teamgate
Files and Attachments
Nutshell
File Attachments
1:1Teamgate file metadata (file name, storage location, size) exports via API, but actual binary files must be downloaded from Teamgate and re-uploaded to Nutshell. We flag file attachment count and total size during scoping. If the customer's Teamgate storage tier (5GB/user Starter, 10GB/user Professional) is near capacity, we identify which files to migrate and which to leave behind, since binary re-upload requires download bandwidth and Nutshell storage allocation on the destination side.
Teamgate
Users
Nutshell
Users
1:1Teamgate user records (name, email, role, active status) export as a user list. We match Teamgate users by email to Nutshell users at migration time. Any Teamgate owner without a matching Nutshell user goes to a reconciliation queue for the customer to provision before record import continues. Inactive Teamgate users are mapped as inactive Nutshell users if their historical assignments on Deals and Activities need to be preserved.
| Teamgate | Nutshell | Compatibility | |
|---|---|---|---|
| People | Contact1:1 | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Deal | Opportunity1:1 | Fully supported | |
| Pipeline | Pipelinelossy | Fully supported | |
| Pipeline Stages | Pipeline Stageslossy | Mapping required | |
| Custom Fields | Custom Fields1:1 | Mapping required | |
| Tags | Tags1:1 | Mapping required | |
| Activities (Tasks, Calls, Emails, Meetings) | Activities1:1 | Fully supported | |
| Files and Attachments | File Attachments1:1 | Mapping required | |
| Users | Users1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Teamgate gotchas
SmartDialer usage billing is uncapped and opaque
Annual vs monthly billing creates a 2.3–3× price swing
Import history does not preserve original source timestamps
Storage tier limits constrain file migration volume
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
Scoping and data audit
We audit the source Teamgate account to count People, Companies, Deals, Activities, custom fields, tags, pipeline definitions, and storage usage. We identify any Teamgate-specific features in active use (SmartDialer usage, workflow rules, integration connections) and document them as non-migratable items. We review the customer's Nutshell destination account to confirm the target tier supports the expected record counts. The scoping output is a written migration scope including record counts, custom field schema, pipeline definitions, and a list of items requiring manual rebuild post-migration.
Schema extraction and destination configuration
We extract the full Teamgate field schema (standard and custom fields, field types, dropdown values) via the Teamgate REST API. We create equivalent custom fields in Nutshell before any data import, matching field types and dropdown option lists. We configure Nutshell pipelines to match the Teamgate pipeline definitions, including stage names, stage order, and probability percentages. Loss reason values are created in Nutshell's settings to match Teamgate's configured dropdown options.
Owner and user reconciliation
We extract every distinct Teamgate owner referenced on Deals and Activities and match by email against the Nutshell destination user list. Owners without a matching Nutshell user are placed in a reconciliation queue. The customer's admin provisions missing Nutshell users before record import begins. Owner assignments on Deals and Activities resolve at migration time using the matched Nutshell user ID.
Sample migration and mapping validation
We run a sample migration of a representative subset of records (typically 50-100 records across People, Companies, Deals, and Activities) into the customer's Nutshell account. The customer's admin reviews the imported records against the Teamgate source, validates field mapping accuracy, and confirms the Company link on Contacts is resolving correctly. Any mapping corrections are applied before the full production migration begins. Nutshell's documented Import2 migration tool supports this sample-first approach.
Production migration in dependency order
We run production migration in record-dependency order: Companies (no dependencies), People as Contacts with Company link resolved, Deals as Opportunities with pipeline stage and owner resolved, Activities (Tasks, Calls, Emails, Meetings) with parent record resolved by Contact or Opportunity ID, and finally file attachment metadata with instructions for binary re-upload. Each phase emits a row-count reconciliation report. File binary downloads and re-uploads run as a parallel track with the data migration to maximize timeline efficiency.
Cutover, final reconciliation, and handoff
We freeze writes to Teamgate during cutover and run a final delta migration of any records modified during the migration window. We deliver a full reconciliation report comparing Teamgate source counts to Nutshell destination counts for every object type, plus a spot-check sample of 25-50 records validated by the customer's admin. We deliver the integration inventory and automation rebuild documents as separate outputs. We support a one-week hypercare window for reconciliation issues. Workflows, sequences, and automation rules are not migrated as code; the inventory document lists each active rule for the customer's admin to rebuild in Nutshell.
Platform deep dives
Teamgate
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
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 Teamgate and Nutshell.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Teamgate: Not publicly documented.
Data volume sensitivity
Teamgate doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Teamgate to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Teamgate to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Teamgate
Other ways to arrive at Nutshell
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.