CRM migration
Field-level mapping, validation, and rollback between GBuilder and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
GBuilder
Source
Nutshell
Destination
Compatibility
11 of 11
objects map 1:1 between GBuilder and Nutshell.
Complexity
BStandard
Timeline
24–72 hours
Overview
GBuilder and Nutshell differ significantly in data model structure and automation philosophy. GBuilder's custom fields require manual pre-creation in Nutshell before migration; Nutshell's custom fields live under Settings > Data > Custom Fields for People, Companies, and Leads. Nutshell's standard objects—People, Companies, Deals, Activities, and Notes—map directly from GBuilder equivalents, though GBuilder's pipeline stages need value-by-value mapping since stage names rarely align. Nutshell's export tools and JSON-RPC API handle incoming data; GBuilder's export path is typically CSV or direct database extraction. We sequence the migration: custom fields first (for planning), then People and Companies, then Deals, Activities, Notes, and Tasks. Owner resolution uses email match against Nutshell users. Activity timestamps and deal probability percentages preserve across both systems. Workflows, email sequences, and automation rules have no equivalent construct in Nutshell and must be rebuilt post-migration—FlitStack AI exports GBuilder configuration data as a rebuild reference for your team. During planning, FlitStack AI delivers a custom field pre-creation checklist and a value-mapping template to streamline field setup. The mapping specification is reviewed with your team before any data transfer begins, ensuring alignment and reducing risk.
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 GBuilder 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.
GBuilder
GBuilder Contact
Nutshell
Nutshell Person
1:1Direct field-level map. All standard person properties—name, email, phone, address—transfer to Nutshell Person. Owner assignment resolves via email match to Nutshell users; any unmatched owners are flagged before migration to prevent orphaned record assignments, and ensure data integrity throughout the process.
GBuilder
GBuilder Company
Nutshell
Nutshell Company
1:1Direct field-level map. Company name, domain, industry, employee count, and annual revenue transfer to Nutshell Company. GBuilder's parent-child company hierarchies preserve via Nutshell's parent company lookup. Multi-company contact associations collapse to a primary company per person, for cleaner record management.
GBuilder
GBuilder Deal
Nutshell
Nutshell Deal
1:1Direct field-level map. Deal name, amount, close date, and owner transfer to Nutshell Deal. GBuilder pipeline stages map to Nutshell stage IDs via value mapping—the actual stage names and probabilities are reconciled during the migration plan before the run commits.
GBuilder
GBuilder Pipeline
Nutshell
Nutshell Deal Pipeline
1:1Pipeline structure transfers as a set of deal categories in Nutshell. GBuilder's stage-to-stage ordering preserves in Nutshell's stage configuration. Probability percentages transfer per stage or fall back to Nutshell defaults based on your approval during the mapping review phase, and validation.
GBuilder
GBuilder Lead
Nutshell
Nutshell Lead
1:1Direct field-level map. Lead status and source information transfer via value mapping—GBuilder's status values map to Nutshell's lead status field. Open, Qualified, and Lost statuses align between systems; custom status values are preserved as custom field values for reference, in Nutshell.
GBuilder
GBuilder Activity
Nutshell
Nutshell Activity
1:1GBuilder calls, emails, and meetings collapse into Nutshell's unified Activity object. Type, subject, date, duration, description, and linked Person or Deal transfer. Original timestamps and owner assignment preserve across both platforms, ensuring accurate history and accountability for each interaction throughout the migration process.
GBuilder
GBuilder Note
Nutshell
Nutshell Note
1:1Note body transfers to Nutshell Note and attaches to the linked Person, Company, or Deal record. GBuilder's note creation timestamps and owner assignment preserve in Nutshell. Rich-text formatting in notes is preserved where GBuilder exports support it, for future reference.
GBuilder
GBuilder Task
Nutshell
Nutshell Task
1:1Task subject, due date, completion status, and linked Person, Company, or Deal transfer to Nutshell Task. Completed/incomplete status maps directly. Task owners resolve via email match to Nutshell users just like Contact and Deal owners, ensuring accurate assignment and follow-up.
GBuilder
GBuilder Custom Field
Nutshell
Nutshell Custom Field
1:1GBuilder custom fields require pre-creation as custom fields in Nutshell before migration. Nutshell stores custom fields under Settings > Data > Custom Fields for People, Companies, and Leads. Field type conversion applies: text fields map to Nutshell short text, pick-lists to Nutshell choices, dates to Nutshell date fields.
GBuilder
GBuilder Attachment
Nutshell
Nutshell File
1:1File attachments associated with GBuilder records transfer to Nutshell Files. Each file re-uploads to Nutshell's file storage and links to the original record (Person, Company, or Deal). File size limits and inline image handling follow Nutshell's upload constraints, and compliance.
GBuilder
GBuilder Owner
Nutshell
Nutshell User
1:1GBuilder owner records match to Nutshell users by email address. Email-match resolution links the owner ID to the corresponding Nutshell user record. Any owners without a matching email in Nutshell are flagged before migration so your team can create the user account or reassign records to a fallback owner.
| GBuilder | Nutshell | Compatibility | |
|---|---|---|---|
| GBuilder Contact | Nutshell Person1:1 | Fully supported | |
| GBuilder Company | Nutshell Company1:1 | Fully supported | |
| GBuilder Deal | Nutshell Deal1:1 | Fully supported | |
| GBuilder Pipeline | Nutshell Deal Pipeline1:1 | Fully supported | |
| GBuilder Lead | Nutshell Lead1:1 | Fully supported | |
| GBuilder Activity | Nutshell Activity1:1 | Fully supported | |
| GBuilder Note | Nutshell Note1:1 | Fully supported | |
| GBuilder Task | Nutshell Task1:1 | Fully supported | |
| GBuilder Custom Field | Nutshell Custom Field1:1 | Fully supported | |
| GBuilder Attachment | Nutshell File1:1 | Fully supported | |
| GBuilder Owner | Nutshell User1: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.
GBuilder gotchas
BIM model files are not exportable via API
Custom project properties vary by project
Approval chain status fields are simplified on export
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
Audit GBuilder data and create Nutshell custom fields
FlitStack AI extracts a full data inventory from GBuilder via CSV export or available API endpoints. We catalog all standard and custom fields, record counts per object, pipeline and stage configurations, and any custom logic or pick-list values. During this phase, your team creates the custom fields in Nutshell under Settings > Data > Custom Fields that correspond to GBuilder custom fields. FlitStack delivers a custom field creation checklist and a value-mapping template for pick-list fields. This phase typically takes 3–5 business days.
Map fields, stages, and owner resolution rules
With the custom fields created, FlitStack AI builds the field-level mapping specification covering all standard and custom fields. Pipeline stage names map to Nutshell stage IDs via value mapping. Owner resolution uses email match against Nutshell users—any owners without matching emails are flagged so your team can create Nutshell accounts or assign a fallback owner. A mapping review meeting validates the specification before any data moves. This phase typically takes 2–3 business days.
Run a sample migration with field-level validation
A representative slice of GBuilder data—typically 100–300 records spanning People, Companies, Deals, Activities, and Notes—migrates to Nutshell first. FlitStack AI generates a field-level diff comparing source values against the destination values so you can verify field mapping accuracy, stage translation, and owner resolution before the full run commits. Sample validation typically takes 1–2 business days. The diff report includes record counts, any mismatched values, and notes on fields that require manual review. This early validation reduces risk and ensures mapping alignment before the bulk migration begins.
Execute full migration with delta-pickup window
The full GBuilder dataset migrates to Nutshell using the approved mapping specification. A 24–48 hour delta-pickup window opens after the initial migration completes, capturing any records created or modified in GBuilder during the cutover period. Your team continues working in GBuilder throughout this window. Once the delta is applied and reconciled, FlitStack AI delivers a final reconciliation report. GBuilder access is revoked at your confirmation. Audit log and rollback capability remain available for 30 days post-migration.
Rebuild email sequences and workflow automation
With data confirmed in Nutshell, your team configures personal email sequences and any workflow automation using Nutshell's native tools (Pro plan). FlitStack AI exports GBuilder configuration data—including sequence logic, custom field automation rules, and lead routing definitions—as a rebuild reference document. This phase runs in parallel with the migration or immediately after, depending on your team's availability. Budget 1–4 weeks for full sequence and automation reconstruction.
Platform deep dives
GBuilder
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
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 GBuilder and Nutshell.
Object compatibility
1 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
GBuilder: Not publicly documented.
Data volume sensitivity
GBuilder 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 GBuilder to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your GBuilder 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 GBuilder
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.