CRM migration
Field-level mapping, validation, and rollback between Goals.com and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Goals.com
Source
Nutshell
Destination
Compatibility
5 of 8
objects map 1:1 between Goals.com and Nutshell.
Complexity
BStandard
Timeline
2-4 weeks
Overview
Goals.com and Nutshell both serve small sales teams at accessible price points, but they differ fundamentally in data model depth and ecosystem maturity. Goals.com stores leads, deals, and sales goals in a flat structure with no published API; extracting data requires manual export or custom scraping routines that we verify against the source before import. Nutshell provides a standard CRM object model (People, Companies, Deals, Activities) with a documented REST API, custom fields for Companies and People, and a pipeline system with configurable stages. The migration maps Goals.com Sales Goals to Nutshell custom fields or linked records, preserves commission history as a custom object, and flags contest scoring rules as non-transferable. Workflows, automations, and goal-triggered alerts do not migrate; we deliver a written inventory of these for your admin to rebuild inside Nutshell.
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 Goals.com 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.
Goals.com
Lead
Nutshell
Person (People)
1:1Goals.com Leads (inquiry capture, grading, and qualification stages) map directly to Nutshell People records. The lead's generation source, grade, and qualification status transfer as custom fields or as values in the built-in status fields available on People. Owner lookup resolves by email match to the corresponding Nutshell User record. If Goals.com stores any territory or team assignment on the lead, we map that to a custom field or Nutshell Team assignment post-import.
Goals.com
Deal
Nutshell
Deal
1:1Goals.com Deal records map 1:1 to Nutshell Deals with deal value, stage name, owner, and close date preserved. Pipeline stages in Goals.com map to Nutshell pipeline stage values in the configured Nutshell pipeline. Custom stage labels from Goals.com require explicit mapping to Nutshell stage names during the scoping phase. Closed-won and closed-lost status and dates transfer as-is.
Goals.com
Sales Goals
Nutshell
Custom fields on Person / Deal / Company
lossyGoals.com Sales Goals (call volume targets, email targets, revenue targets) have no native Nutshell equivalent. We export goal definitions, target values, and the associated time period (monthly, quarterly, annual). During migration we create custom fields on Person, Deal, or Company records to hold these target values, with a naming convention that preserves the original goal name and period. Progress percentages are recalculated post-import based on actual activity logged in Nutshell.
Goals.com
Pipeline Stages
Nutshell
Nutshell Pipeline Stage
1:1Goals.com pipeline stages map to Nutshell pipeline stage values in the configured Nutshell pipeline. Stage order and probability (if stored in Goals.com) transfer as stage metadata in Nutshell. We preserve the stage history log from Goals.com as custom activity records or linked notes on the Deal so the full pipeline journey is visible post-migration.
Goals.com
Commission
Nutshell
Custom fields on Person / Deal
lossyGoals.com commission records (payout amounts, associated deals, rep assignments, payout dates) export as data. We import these as custom fields on the linked Nutshell Person and Deal records, creating a commission history that shows payout amounts and associated deal outcomes. Active payout rules, tiered commission structures, and incentive scoring logic do not transfer; these require manual rebuild post-migration, and we provide a commission schema template to guide that work.
Goals.com
User Account
Nutshell
Nutshell User
1:1Goals.com user accounts with role assignments (manager vs rep) migrate to Nutshell Users. Owner lookups on Leads, Deals, and Activities resolve by email match to Nutshell User records. We extract the team membership data from Goals.com and map it to Nutshell Teams or Groups. Any Goals.com user without a matching email in the destination Nutshell org is held in a reconciliation queue for the customer's admin to provision before the record import phase begins.
Goals.com
Activity Tracking
Nutshell
Nutshell Activity Log
1:1Goals.com notes, reminders, and customer interaction logs migrate as Nutshell Activities attached to the corresponding Person or Deal. We extract the activity type, timestamp, author, and content. Because Goals.com does not store a full audit trail of every system event, historical activity completeness depends on what is available in the Goals.com export. We document any gaps in the activity history in the pre-import gap report provided to the customer.
Goals.com
Sales Contest
Nutshell
Custom object or linked records (historical results only)
lossyGoals.com contest definitions and historical results export as data. Active contest scoring rules, point allocations, and leaderboard logic are application-level rules that do not transfer and require manual re-creation at the destination. We provide a contest schema template with historical results included so the customer's admin can configure the same contest logic in Nutshell or a dedicated incentive compensation tool post-migration. Leaderboard history migrates as a custom object with rep name, contest period, points earned, and rank.
| Goals.com | Nutshell | Compatibility | |
|---|---|---|---|
| Lead | Person (People)1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Sales Goals | Custom fields on Person / Deal / Companylossy | Mapping required | |
| Pipeline Stages | Nutshell Pipeline Stage1:1 | Fully supported | |
| Commission | Custom fields on Person / Deallossy | Fully supported | |
| User Account | Nutshell User1:1 | Fully supported | |
| Activity Tracking | Nutshell Activity Log1:1 | Mapping required | |
| Sales Contest | Custom object or linked records (historical results only)lossy | 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.
Goals.com gotchas
No documented public API for data extraction
Flat objective hierarchy limits strategic data modeling
Notification redundancy not exportable
Contest and incentive logic not transferable
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
Discovery and data audit
We audit the source Goals.com account for record counts across Leads, Deals, Sales Goals, Commission records, User Accounts, Team memberships, Activity logs, and any Sales Contest history. Because Goals.com has no public API, this phase includes a manual data export walkthrough with the customer to identify which datasets are accessible through Goals.com's export functionality and which require custom extraction routines. We document the data completeness report and flag any records that may be incomplete or inaccessible before mapping begins.
Mapping design and Nutshell custom field provisioning
We design the mapping from Goals.com objects to Nutshell objects, with specific attention to Sales Goals and Commission data that require custom fields in Nutshell. We provision custom fields on Nutshell People, Companies, and Deals for goal target values, commission amounts, and contest history before any data import. Pipeline stages from Goals.com map to Nutshell pipeline stages, and we configure the Nutshell pipeline structure (stages, probabilities, order) to match the source. This design is validated against the data completeness report from step one.
User provisioning and owner reconciliation
We extract every distinct Goals.com user referenced on Leads, Deals, Activities, and Commission records and match by email against the Nutshell destination's User table. Goals.com team memberships map to Nutshell Teams. Any Goals.com user without a matching Nutshell User account goes to a reconciliation queue; the customer's admin provisions missing Nutshell Users before record migration proceeds. Owner lookups on all imported records depend on this step completing first.
Data extraction, transformation, and Nutshell import
We run data extraction from Goals.com using the agreed export routines, verify row counts, and spot-check record completeness. We then transform the data to match Nutshell's field types and required formats, resolve all owner references through the mapping table built in step three, and import in dependency order: Nutshell Users first (already provisioned), then People (from Goals.com Leads), then Companies, then Deals (with custom goal and commission fields populated), then Activities. Each phase emits a row-count reconciliation report before the next begins.
Cutover, delta sync, and post-migration checklist delivery
We freeze Goals.com writes during cutover, run a final delta migration of any records modified during the migration window, then switch the team to Nutshell as the system of record. We deliver the post-migration checklist including: custom field and goal configuration notes, commission schema template for active payout rule rebuild, contest schema template for contest logic re-creation, notification preference reconfiguration guide for each user, and a written inventory of any Goals.com workflows, automations, or goal-triggered alerts that require manual rebuild in Nutshell.
Platform deep dives
Goals.com
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 Goals.com 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
Goals.com: Not publicly documented.
Data volume sensitivity
Goals.com 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 Goals.com to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Goals.com 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 Goals.com
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.