CRM migration
Field-level mapping, validation, and rollback between Planado and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Planado
Source
Nutshell
Destination
Compatibility
11 of 12
objects map 1:1 between Planado and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
Planado and Nutshell occupy different functional niches. Planado is a field service management platform built around jobs, technicians, GPS tracking, and operational checklists for mobile workers. Nutshell is a sales CRM designed for lead management, pipeline tracking, and customer relationship recording. The migration from Planado to Nutshell is therefore a data-model translation exercise: operational job records must become Deals or custom-field records in Nutshell, clients must become Companies or People records, and employee records become Nutshell users or are held for manual re-invitation. FlitStack AI extracts Planado data via its REST API (api.planadoapp.com) using authenticated read access. We pull clients, jobs, locations, employees, checklists, and report attachments. The extraction runs in read-only mode against Planado — your dispatchers continue scheduling without interruption. A delta-pickup window of 24–48 hours captures any records created or updated during the cutover window. On the Nutshell side, we write via the JSON-RPC API (app.nutshell.com/api/v1/json) using Basic authentication scoped to your account. Nutshell's standard objects (People, Companies, Leads, Deals, Activities) receive direct-mapped fields. Planado checklists, custom job attributes, and GPS-derived data have no native Nutshell equivalent — those migrate as custom fields on the relevant Nutshell object or as attached notes for reference. Workflows, scheduling rules, routing logic, and automation triggers in Planado do not migrate; we export Planado's workflow definitions as a PDF reference document for your team to rebuild in Nutshell manually or via Nutshell's automation tools.
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 Planado 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.
Planado
Client
Nutshell
Company / Person
1:1Planado clients with a business name map to Nutshell Company records. The Company Name, website, industry, and address fields transfer directly. Individual clients without a company name (e.g., residential customers) map to Nutshell Person records. We preserve the original Planado client ID as Source_System_ID__c for traceability and delta-run de-duplication.
Planado
Job
Nutshell
Deal
1:1Planado jobs translate to Nutshell Deals. The job name becomes the Deal name, the current job status maps to a Deal stage via value mapping (Open jobs → Open stages; Completed → Closed Won; Cancelled → Closed Lost), and the job description becomes the Deal description. Job priority, time window, and service category migrate as custom fields on the Deal.
Planado
Employee
Nutshell
User
1:1Planado employee records with active email addresses map to Nutshell User accounts. FlitStack resolves each employee email against Nutshell users by email match. Employees without a Nutshell account are flagged before migration — your team can invite them or assign their records to a fallback owner. Note: Planado GPS, availability schedule, and routing data have no Nutshell equivalent and do not transfer.
Planado
Location / Site
Nutshell
Company (address fields) / Activity
many:1Planado locations (service sites) merge with the client Company record in Nutshell. Multiple visits at the same location collapse to the primary Company address. For locations without a named client (e.g., recurring site maintenance), we create a standalone Nutshell Company with the location address and a reference to the job as a Deal.
Planado
Job Checklist
Nutshell
Custom fields on Deal / Note
1:1Planado job checklists have no native Nutshell equivalent. We extract checklist item names and completion status as custom fields on the Nutshell Deal (e.g., Checklist_Item_1__c, Checklist_Completed__c). For multi-step checklists exceeding 10 items, we attach a formatted Note to the Deal with the full checklist and check states for reference.
Planado
Job Report
Nutshell
Note / Attachment
1:1Planado job reports (photos, notes, signatures) migrate as Nutshell Notes attached to the corresponding Deal. Photos download from Planado and re-upload as Nutshell attachments (25MB file limit applies per Nutshell). Client signatures migrate as PNG attachments on the Deal record. Timestamps and technician name on the report are preserved in the Note body.
Planado
Job Status History
Nutshell
Custom datetime fields on Deal
1:1Planado records every status transition on a job (en route, started, finished, etc.) with timestamps. We surface the most recent status change as a custom datetime field (Last_Status_Change__c) on the Nutshell Deal. Full status history appends as a Note for audit purposes since Nutshell Deals have a limited activity timeline compared to Planado's job log.
Planado
Custom Job Type
Nutshell
Custom field on Deal
1:1Planado custom job types (e.g., HVAC Repair, Cleaning, Installation) that don't map to a standard Nutshell field become Deal-level custom pick-list fields (Job_Type__c). If a Planado account uses more than 5 custom job types, we group them into categories to avoid creating an unwieldy pick-list in Nutshell.
Planado
Equipment / Asset
Nutshell
Custom field on Company or Deal
1:1Planado equipment records linked to a job map to custom fields on the related Nutshell Company (if a shared asset) or Deal (if job-specific). Equipment serial numbers, model numbers, and install dates become text or date fields. Assets not linked to a specific client become standalone custom fields on the Deal.
Planado
Attachment / Photo
Nutshell
Nutshell Attachment
1:1Job photos, signatures, and PDF reports export from Planado and re-upload to Nutshell via the Nutshell API attachment endpoint. Each attachment links to the corresponding Deal record. Files exceeding 25MB are split or linked via an external URL reference stored in a custom Note. Inline images in Planado notes download and rehost as Nutshell attachments.
Planado
Scheduling Rules / Dispatch Logic
Nutshell
No equivalent in Nutshell
1:1Planado's dispatcher scheduling rules, route optimization settings, urgent-job flags, and time-window constraints do not map to any Nutshell object. These represent operational logic native to Planado's FSM engine. We export the scheduling configuration as a PDF reference document for your team to evaluate Nutshell's calendar integrations or third-party scheduling tools post-migration.
Planado
GPS / Route Data
Nutshell
No equivalent in Nutshell
1:1Planado tracks technician GPS coordinates and route history in real time. Nutshell has no GPS, routing, or map-based workforce management features. GPS data does not transfer. We preserve the last known address from Planado as a custom text field on the Nutshell User record for reference only.
| Planado | Nutshell | Compatibility | |
|---|---|---|---|
| Client | Company / Person1:1 | Fully supported | |
| Job | Deal1:1 | Fully supported | |
| Employee | User1:1 | Fully supported | |
| Location / Site | Company (address fields) / Activitymany:1 | Fully supported | |
| Job Checklist | Custom fields on Deal / Note1:1 | Fully supported | |
| Job Report | Note / Attachment1:1 | Fully supported | |
| Job Status History | Custom datetime fields on Deal1:1 | Fully supported | |
| Custom Job Type | Custom field on Deal1:1 | Fully supported | |
| Equipment / Asset | Custom field on Company or Deal1:1 | Fully supported | |
| Attachment / Photo | Nutshell Attachment1:1 | Fully supported | |
| Scheduling Rules / Dispatch Logic | No equivalent in Nutshell1:1 | Fully supported | |
| GPS / Route Data | No equivalent in Nutshell1: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.
Planado gotchas
No public bulk export endpoint for full data migration
Pricing not publicly documented
Custom checklist step media attachments require separate file handling
Zapier integration scope creates automation dependency risk
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 Planado data inventory and identify migration scope
FlitStack AI connects to Planado via read-only API access and inventories all clients, jobs, locations, employees, checklists, and attachments. We generate a data inventory report showing record counts per object, custom field count per job type, attachment sizes, and any non-standard job types or client categories. This report defines the migration scope and informs custom field creation requirements in Nutshell. Your team reviews and approves the scope before we proceed.
Pre-create Nutshell custom fields and map pipeline stages
Before data moves, your Nutshell admin (or our team) creates the custom fields required for Planado data — Job_Type__c, Priority__c, Last_Status_Change__c, Checklist fields, Latitude__c, Longitude__c, Source_System_ID__c, and Original_Create_Date__c. We also map Planado job statuses to your Nutshell Deal stages. Nutshell Enterprise is required for API access during migration. We deliver a field creation checklist and a status-mapping spreadsheet based on the Planado data audit.
Migrate Companies and People before Deals to satisfy foreign-key constraints
Nutshell requires a Company or Person to exist before a Deal can be linked to it. We sequence the migration so that Planado clients (as Companies or Persons) land in Nutshell first, then employees (as Users) are resolved, then jobs map to Deals with company_id links. Planado client IDs are stored as Source_System_ID__c on each Nutshell record so that the job-to-client link resolves correctly during the migration run. Unresolved employee emails are flagged for manual Nutshell invitation before Deals are created.
Run sample migration and generate field-level diff
A representative slice of Planado data — typically 100–500 records across multiple job types, clients, and employees — migrates first. We generate a field-level diff comparing source values in Planado to destination values in Nutshell. You verify that job types, priority, statuses, checklist fields, addresses, and owner resolution look correct. Any mapping errors surface here before the full run commits. Sample migration typically completes in 2–4 hours.
Execute full migration with delta-pickup window
The full Planado dataset migrates to Nutshell via the JSON-RPC API. A delta-pickup window of 24–48 hours runs concurrently: any records created or updated in Planado during the cutover window are captured and written to Nutshell after the main run completes. FlitStack generates an audit log of every operation — record created, updated, or skipped — with source and destination IDs. One-click rollback reverts all migrated records if reconciliation fails. Your team continues working in Planado during the entire cutover window.
Platform deep dives
Planado
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 Planado 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
Planado: Not publicly documented as a hard ceiling. Planado offers to add additional API endpoints free of charge for integration needs that exceed standard scope..
Data volume sensitivity
Planado 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 Planado to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Planado 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 Planado
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.