CRM migration
Field-level mapping, validation, and rollback between Trade Service Pro and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Trade Service Pro
Source
Nutshell
Destination
Compatibility
11 of 12
objects map 1:1 between Trade Service Pro and Nutshell.
Complexity
BStandard
Timeline
24–72 hours
Overview
Trade Service Pro and Nutshell CRM occupy different positions in the SMB stack. Trade Service Pro combined CRM, scheduling, job management, and invoicing into a single platform for field service businesses — contractors, HVAC technicians, plumbers, and electricians. Nutshell is a standalone sales CRM built for small and mid-market teams, offering contact management, deal pipelines, and email integration without native field service operations. The migration requires decomposing Trade Service Pro's unified records into Nutshell's three core object types — People (contacts), Companies, and Leads — while routing job and service records into Nutshell's Tasks and Activity model. FlitStack AI uses Trade Service Pro's API or data export to extract all customers, companies, job records, invoices, and custom forms. We apply field-level mapping to each record type, create any custom fields required in Nutshell, and sequence the migration so foreign keys resolve correctly. Workflows, automations, and custom forms do not transfer — FlitStack exports your form definitions and workflow logic as a rebuild reference for your Nutshell admin.
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 Trade Service Pro 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.
Trade Service Pro
Customer
Nutshell
Person
1:1Trade Service Pro customer records map directly to Nutshell People objects. All contact fields — name, email, phone, address, and custom properties — transfer to matching or custom fields on Person. Owner resolution happens by email match against Nutshell users.
Trade Service Pro
Customer (primary company link)
Nutshell
Company
1:1Trade Service Pro stores a primary company on each customer record. That company link migrates as a Company record in Nutshell, then associates back to the Person via Nutshell's company-person relationship. Companies without any contacts route to a standalone Company import.
Trade Service Pro
Company (branch/location)
Nutshell
Company
many:1Trade Service Pro allows multiple company locations per customer. These locations are merged into a single Nutshell Company record, with each distinct location captured in a custom text field (Location_Branch__c). Because Nutshell lacks native multi‑location company hierarchies, the Location_Branch__c field preserves the branch identifier, address line, or site name from Trade Service Pro, enabling your team to reference the original location context within the unified company record.
Trade Service Pro
Job
Nutshell
Task
1:1Trade Service Pro job records become Nutshell Tasks. Job type, status, description, and scheduled date map to Task subject, status, description, and due date respectively. Technician assignment becomes Task owner. Original job create date and last-modified date are preserved as custom datetime fields.
Trade Service Pro
Job (service history)
Nutshell
Activity
1:1Each completed job generates a Nutshell Activity log entry capturing the service performed, outcome, and technician notes. The activity records the job completion date, service type, and resolution details. Multiple service events on a single job become separate activity entries, each linked to the same Person and Company so that the service history appears in the customer timeline. FlitStack maps the activity type to a custom field (Service_Type__c) for filtering.
Trade Service Pro
Invoice
Nutshell
Activity + Custom Fields
1:1Nutshell has no native invoice object, so invoice records are migrated as Activities with custom fields for Invoice_Amount__c, Invoice_Status__c, and Balance_Due__c. Each activity’s description summarizes the line items as plain text, listing item, quantity, and price. Full invoice PDFs are attached directly to the activity for reference. Your team should reconcile invoice totals against Trade Service Pro reports before closing the source system, as Nutshell does not store payment data.
Trade Service Pro
Proposal
Nutshell
Activity + Custom Fields
1:1Trade Service Pro proposals map to Nutshell Activities with custom fields for Proposal_Value__c and Proposal_Status__c. Proposal body text goes into the activity notes. Nutshell Pro plans include a Quotes feature — FlitStack can create Nutshell Quotes from migrated proposals if your plan supports it.
Trade Service Pro
Lead (intake)
Nutshell
Lead
1:1Trade Service Pro intake records that represent prospective customers rather than active service relationships map directly to Nutshell Leads. Ad source, lead notes, and custom intake form fields migrate to matching or custom fields on the Lead object. FlitStack also preserves the original lead creation date as a custom datetime field (TSP_Created_Date__c) and maps the lead status to Nutshell’s built-in status picklist, ensuring a lead pipeline view from day one.
Trade Service Pro
Custom Form
Nutshell
Custom Fields (People / Company / Lead)
1:1Trade Service Pro custom forms are object-specific intake instruments. Each form field becomes a Nutshell custom field on the relevant object type (Person, Company, or Lead). Multi-select or conditional form logic is simplified — Nutshell supports picklist and text custom fields but not conditional branching.
Trade Service Pro
Pricebook / Product
Nutshell
Custom Fields or Activity Notes
1:1Trade Service Pro's pricebook stores products, services, and labor rates with tax-rate associations. Nutshell has no native product catalog. Service descriptions and rates are preserved as a custom Product_Services__c text field on relevant records — your team rebuilds the pricebook in Nutshell manually or via spreadsheet import.
Trade Service Pro
User / Team Member
Nutshell
User
1:1Trade Service Pro user accounts resolve to Nutshell users by email match. Active users who exist in both systems get their records assigned to the matched Nutshell user. Users who only exist in Trade Service Pro are flagged as unmapped — you create their Nutshell accounts before migration commits.
Trade Service Pro
Attachment / File
Nutshell
Activity Attachment or External Link
1:1Trade Service Pro file attachments on customers, jobs, or invoices are exported and re-hosted. Small files attach directly to the corresponding Nutshell Activity. Large files (photos, inspection reports) are stored externally with a link field added to the activity record.
| Trade Service Pro | Nutshell | Compatibility | |
|---|---|---|---|
| Customer | Person1:1 | Fully supported | |
| Customer (primary company link) | Company1:1 | Fully supported | |
| Company (branch/location) | Companymany:1 | Fully supported | |
| Job | Task1:1 | Fully supported | |
| Job (service history) | Activity1:1 | Fully supported | |
| Invoice | Activity + Custom Fields1:1 | Fully supported | |
| Proposal | Activity + Custom Fields1:1 | Fully supported | |
| Lead (intake) | Lead1:1 | Fully supported | |
| Custom Form | Custom Fields (People / Company / Lead)1:1 | Fully supported | |
| Pricebook / Product | Custom Fields or Activity Notes1:1 | Fully supported | |
| User / Team Member | User1:1 | Fully supported | |
| Attachment / File | Activity Attachment or External Link1: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.
Trade Service Pro gotchas
No public API forces reliance on in-app CSV exports
Active timesheet timers do not export in CSV
eSign status on Proposals does not carry over
Attachment bulk download requires separate handling
No schema documentation complicitates field mapping
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
Inventory Trade Service Pro data via API and export
FlitStack AI connects to Trade Service Pro's data export or API to pull a complete record inventory: all customers, companies, jobs, invoices, proposals, pricebook entries, and custom form definitions. We count records per object, identify fields in active use, and flag records with missing critical data (no email, no owner) that need cleanup before migration. This inventory also reveals the density of job history — deeply historical job records that exceed your reporting window can be filtered to reduce migration scope.
Map objects and create Nutshell custom fields
Based on the inventory, FlitStack AI generates an object-mapping plan and a custom-field creation list for Nutshell. We create the custom fields (tsp_job_id__c, Invoice_Amount__c, etc.) in your Nutshell account before migration runs, so field IDs exist at validation time. The mapping plan covers every object: Customers to People, Jobs to Tasks, Invoices to Activities with custom fields, Leads to Nutshell Leads. You review and approve the plan before any data moves.
Run sample migration with field-level diff
A representative slice — typically 100–500 records spanning customers, companies, jobs, and invoices — migrates to Nutshell first. FlitStack AI generates a field-level diff comparing source values to destination values for every mapped field, including custom fields. You verify that job-to-task conversion looks correct, invoice amounts landed in the right custom fields, and owner resolution by email match produced expected assignments. Any mapping adjustments happen before the full run.
Execute full migration with delta pickup
The full migration runs in sequenced batches: Companies first (foreign key dependency), then People and Leads, then Jobs as Tasks, then Invoices and Proposals as Activities. A delta-pickup window (typically 24–48 hours) captures any records modified in Trade Service Pro during cutover. FlitStack AI performs record-count reconciliation against the source export and flags any records that skipped due to data quality issues. An audit log records every operation for rollback reference.
Export workflow definitions and deliver rebuild reference
Trade Service Pro workflows, sequences, and custom form definitions are exported as JSON or structured documents. These serve as a rebuild reference for your Nutshell admin when setting up Nutshell's automation tools. FlitStack does not migrate automations — they require destination-platform logic to function. We also deliver a post-migration report summarizing record counts, any records skipped, and custom field setup instructions so your team can validate totals and go live.
Platform deep dives
Trade Service Pro
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 Trade Service Pro 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
Trade Service Pro: Not publicly documented.
Data volume sensitivity
Trade Service Pro 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 Trade Service Pro to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Trade Service Pro 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 Trade Service Pro
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.