CRM migration
Field-level mapping, validation, and rollback between GorillaDesk and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
GorillaDesk
Source
Nutshell
Destination
Compatibility
12 of 12
objects map 1:1 between GorillaDesk and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
GorillaDesk organizes field-service operations around customers, jobs, schedules, and technicians — a model built for dispatch, routing, and on-site service delivery. Nutshell organizes sales around People, Companies, Leads, and Deals with pipeline stages tied to sales-closing activity. The structural gap is significant: GorillaDesk has no native deal or pipeline concept, while Nutshell has no native scheduling or job-status model. FlitStack AI handles this by mapping GorillaDesk customers to Nutshell People (with linked Companies), GorillaDesk jobs to Nutshell Deals or Activities depending on service type and stage, and GorillaDesk notes to Nutshell notes. Technician and user records in GorillaDesk map to Nutshell users by email match. We use GorillaDesk's REST API with token authentication for extraction and Nutshell's JSON-RPC API for load, respecting rate limits on both sides. A delta-pickup window (24–48 hours) captures any records modified during the cutover window. Workflows, automations, VoIP configurations, and integrations do not migrate — those require manual rebuild in Nutshell's settings or via its API.
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 GorillaDesk 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.
GorillaDesk
Customer
Nutshell
Person
1:1GorillaDesk customers map 1:1 to Nutshell People. Name, email, phone, address, and notes carry over directly. The primary company association in GorillaDesk (if any) creates a linked Nutshell Company record. Customer create/update timestamps are preserved as custom datetime fields in Nutshell since Nutshell's native created/modified dates reflect migration time, not the original record age.
GorillaDesk
Customer (company name populated)
Nutshell
Company
1:1When a GorillaDesk customer has a company/organization name field populated, FlitStack AI creates a corresponding Nutshell Company record and links the Person record to it via the AccountId relationship. If multiple GorillaDesk customers share the same company name, they all link to the same Nutshell Company. This prevents duplicate company records and mirrors GorillaDesk's N:1 customer-to-company association model.
GorillaDesk
Job
Nutshell
Deal / Activity
1:1GorillaDesk jobs don't map to a single Nutshell object — the correct destination depends on job type. Recurring or revenue-generating service jobs (with a dollar amount) map to Nutshell Deals with a 'Service Delivery' pipeline stage, preserving the amount, service date, and linked Person/Company. One-off administrative or internal jobs map to Nutshell Activities (calls or tasks) with a note field capturing the job description. The transformation decision is driven by whether the GorillaDesk job has an invoice amount attached.
GorillaDesk
Job Status
Nutshell
Deal Stage / Activity Status
1:1GorillaDesk job statuses (Scheduled, In Progress, Completed, Cancelled) map to Nutshell Deal stages or Activity completion flags via value-by-value lookup. 'Scheduled' maps to a custom 'Service Scheduled' deal stage; 'Completed' maps to 'Closed Won' with the original service date preserved in a custom field; 'Cancelled' maps to 'Closed Lost' with a cancellation reason note. The mapping is configured in the migration plan before the run.
GorillaDesk
User (Technician)
Nutshell
User
1:1GorillaDesk user accounts (technicians, dispatchers, office staff) map to Nutshell users by email address. FlitStack AI matches the email field on each GorillaDesk user record against Nutshell user emails to resolve OwnerId. Unmatched users are flagged before migration so you can either create their Nutshell account or assign their records to a fallback owner. Technicians who are also Nutshell users get assigned as Deal owners for their service jobs.
GorillaDesk
Note
Nutshell
Note
1:1GorillaDesk notes attached to customers or jobs migrate as Nutshell notes on the corresponding Person or Deal record. Original create timestamps and note author are preserved where available via the API. Nutshell's note format is plain text with optional HTML — rich formatting in GorillaDesk notes is converted to plain text during extraction to avoid rendering issues in Nutshell.
GorillaDesk
Phone Type
Nutshell
Phone (custom field)
1:1GorillaDesk distinguishes between phone number types (mobile, work, home, fax) as separate fields. Nutshell has a single phone field on Person records. FlitStack AI maps the primary phone to the standard Phone field and creates custom fields (Mobile__c, Work_Phone__c, Home_Phone__c) on the Nutshell Person object for additional phone types. These custom fields are created in Nutshell before the migration run.
GorillaDesk
Attachment / Photo
Nutshell
File Attachment
1:1GorillaDesk file attachments (photos, signatures, documents on jobs and customers) are downloaded from GorillaDesk's file storage and re-uploaded to Nutshell as attachments on the corresponding Person or Deal record. File size limits apply on the Nutshell side based on your storage plan. Inline images in GorillaDesk notes are extracted and re-hosted as Nutshell file attachments to preserve visual context in service records.
GorillaDesk
Custom Field (Customer)
Nutshell
Custom Field (Person)
1:1GorillaDesk custom fields on customers (e.g., 'Preferred Service Day', 'Account Type', 'Referral Source') are read from the API response and pre-created in Nutshell on the Person object before migration. Field type is inferred from GorillaDesk's data (text, number, date, picklist) and matched to the closest Nutshell custom field type. Picklist values are mapped value-by-value.
GorillaDesk
Custom Field (Job)
Nutshell
Custom Field (Deal / Activity)
1:1GorillaDesk custom fields on jobs (e.g., 'Chemicals Used', 'Service Type', 'Equipment Model') map to custom fields on the corresponding Nutshell Deal or Activity depending on where the job landed. Chemical and equipment data from pest control or pool service jobs becomes custom fields on the Deal record in Nutshell for reference and compliance reporting.
GorillaDesk
Lead (GorillaDesk lead source)
Nutshell
Lead
1:1GorillaDesk does not have a native lead concept — incoming inquiries arrive as customers or are captured via web forms. If your GorillaDesk setup uses a customer tag or source field to distinguish new inquiries from established customers, FlitStack AI routes those to Nutshell Leads rather than People based on a configurable tagging rule. Source field values (Google, Referral, Walk-in) map to Nutshell Lead source pick-list values.
GorillaDesk
GPS / Route Data
Nutshell
No equivalent
1:1GorillaDesk tracks technician GPS coordinates and route assignments for scheduling optimization. Nutshell has no routing, GPS, or field-technician dispatch model — this data has no native equivalent. FlitStack preserves route and GPS data as a custom Activity note or as an attachment on the related Deal for historical reference, but it cannot activate as live routing in Nutshell. If routing is critical, consider retaining GorillaDesk for field operations alongside Nutshell for CRM.
| GorillaDesk | Nutshell | Compatibility | |
|---|---|---|---|
| Customer | Person1:1 | Fully supported | |
| Customer (company name populated) | Company1:1 | Fully supported | |
| Job | Deal / Activity1:1 | Fully supported | |
| Job Status | Deal Stage / Activity Status1:1 | Fully supported | |
| User (Technician) | User1:1 | Fully supported | |
| Note | Note1:1 | Fully supported | |
| Phone Type | Phone (custom field)1:1 | Fully supported | |
| Attachment / Photo | File Attachment1:1 | Fully supported | |
| Custom Field (Customer) | Custom Field (Person)1:1 | Fully supported | |
| Custom Field (Job) | Custom Field (Deal / Activity)1:1 | Fully supported | |
| Lead (GorillaDesk lead source) | Lead1:1 | Fully supported | |
| GPS / Route Data | No equivalent1: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.
GorillaDesk gotchas
API lacks bulk export and invoice/job endpoints
Customer CSV imports require a paid plan and support involvement
Reporting data may be inaccessible for Basic plan customers
GPS tracking and materials data are add-on gated
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
Connect FlitStack AI to GorillaDesk and Nutshell APIs
FlitStack AI authenticates to GorillaDesk using your per-company API token (generated in the Addons → API page) and to Nutshell using your username and API key via HTTP Basic auth. We run a connection check on both APIs to confirm read access on GorillaDesk and write access on Nutshell. If GorillaDesk's rate limits return a 429 response, the engine pauses for the rate_reset duration before retrying. This step also pulls the field schema from both platforms so we can generate the field-level mapping plan before any data moves.
Generate Nutshell schema plan and pre-create custom fields
Based on GorillaDesk's exported field list, FlitStack AI generates a Nutshell field-creation checklist listing each custom field name, target object (Person, Company, Deal), type (text, number, date, pick-list), and any pick-list values that need mapping. Your Nutshell admin creates these fields in Settings → Customize Fields before the migration run. Simultaneously, we configure the Nutshell pipeline and stages to match GorillaDesk job statuses. This step runs in parallel with your Nutshell admin's field setup and typically takes 2–3 days depending on the number of custom fields.
Run sample migration with field-level diff
A representative slice of 100–500 GorillaDesk records migrates first — spanning customers, companies, jobs, notes, and any records with custom fields. FlitStack AI generates a field-level diff showing the source value, mapped destination field, and any transformation applied (value mapping, custom field creation, note conversion). You review the diff to confirm that job statuses map to the correct Nutshell pipeline stages, technician assignments resolve to Nutshell users, and GorillaDesk custom fields land in the right Nutshell custom fields. No full migration run commits until you approve the sample.
Execute full migration with delta-pickup cutover
After sample approval, FlitStack AI runs the full migration in the correct sequence: Companies first (for account linkage), then People (resolving company links), then Deals (linking to People and assigning owners), then Notes and Attachments (tied to their parent records). The migration engine pauses at the cutover point and opens a delta-pickup window — typically 24–48 hours — during which your team continues working in GorillaDesk. Any records created or modified during this window are captured in a delta run and appended to Nutshell before the final reconciliation. Audit log captures every record written with source system ID for rollback identification.
Reconcile, validate, and deliver rollback playbook
FlitStack AI runs a reconciliation check comparing record counts and field completeness between GorillaDesk and Nutshell. A mismatch report flags any records that failed to migrate, were truncated, or landed in an unexpected field. You can download this report and direct FlitStack AI to re-migrate specific record sets. If reconciliation fails beyond acceptable thresholds, the one-click rollback reverts all Nutshell records written during the migration run — the GorillaDesk account is unaffected. We also deliver a rebuild reference document for your Nutshell admin covering the GorillaDesk workflows, automations, and VoIP configurations that require manual rebuild in Nutshell settings.
Platform deep dives
GorillaDesk
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 GorillaDesk 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
GorillaDesk: Not publicly documented; a 429 response indicates rate limiting and requires exponential backoff.
Data volume sensitivity
GorillaDesk 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 GorillaDesk to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your GorillaDesk 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 GorillaDesk
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.