CRM migration

Migrate from Trade Service Pro to Nutshell

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 logo

Trade Service Pro

Source

Nutshell

Destination

Nutshell logo

Compatibility

92%

11 of 12

objects map 1:1 between Trade Service Pro and Nutshell.

Complexity

BStandard

Timeline

24–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Trade Service Pro logo

Trade Service Pro

What's pushing teams away

  • No public API means third-party integrations or automated data pipelines are not possible, pushing growing companies toward platforms like ServiceTitan or Jobber that offer developer access.
  • Support is ticket-based with no clear SLA, and several reviews of similar FSM platforms cite slow response times as a reason for switching.
  • Limited scalability beyond 11–50 employees means companies that grow past that range often need a more robust platform with advanced dispatch and reporting.
  • Sync issues and reliability bugs, reported across comparable FSM tools, cause field teams to lose confidence in the system during active jobs.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How Trade Service Pro objects map to Nutshell

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

maps to

Nutshell

Person

1:1
Fully supported

Trade 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)

maps to

Nutshell

Company

1:1
Fully supported

Trade 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)

maps to

Nutshell

Company

many:1
Fully supported

Trade 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

maps to

Nutshell

Task

1:1
Fully supported

Trade 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)

maps to

Nutshell

Activity

1:1
Fully supported

Each 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

maps to

Nutshell

Activity + Custom Fields

1:1
Fully supported

Nutshell 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

maps to

Nutshell

Activity + Custom Fields

1:1
Fully supported

Trade 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)

maps to

Nutshell

Lead

1:1
Fully supported

Trade 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

maps to

Nutshell

Custom Fields (People / Company / Lead)

1:1
Fully supported

Trade 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

maps to

Nutshell

Custom Fields or Activity Notes

1:1
Fully supported

Trade 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

maps to

Nutshell

User

1:1
Fully supported

Trade 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

maps to

Nutshell

Activity Attachment or External Link

1:1
Fully supported

Trade 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.

Gotchas + challenges

What specifically takes care here

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 logo

Trade Service Pro gotchas

High

No public API forces reliance on in-app CSV exports

Medium

Active timesheet timers do not export in CSV

Medium

eSign status on Proposals does not carry over

Low

Attachment bulk download requires separate handling

Medium

No schema documentation complicitates field mapping

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • Nutshell has no native invoice or payment object

    Trade Service Pro's invoice records have no direct equivalent in Nutshell's object model. FlitStack AI migrates invoices as Activity records with custom currency fields (Invoice_Amount__c, Invoice_Status__c, Balance_Due__c) and the invoice PDF attached. Nutshell's own Quotes feature (Pro plans) can serve as a forward-looking quoting tool, but historical invoices must be maintained as custom-field activities. Your accounting team should reconcile totals against Trade Service Pro reports before closing the old system.

  • Job scheduling does not map to any Nutshell object

    Trade Service Pro's native job scheduling, dispatch board, and technician assignment have no equivalent in Nutshell's Task model. Nutshell Tasks support due dates and owner assignment, but not time-slot scheduling, recurring service intervals, or route-based dispatch. FlitStack AI converts job records to Tasks with the scheduled date as the due date and the technician as the task owner, but the calendar-based scheduling UX must be rebuilt using Nutshell's calendar integration or a separate scheduling add-on.

  • Pricebook and service catalog have no Nutshell equivalent

    Trade Service Pro's pricebook stores products, services, labor rates, and tax‑rate associations by zip code. Nutshell lacks a native product or service catalog, so service descriptions and rates are preserved as a custom text field (Product_Services_List__c) on relevant records for reference. To build a usable catalog in Nutshell, your admin can import the pricebook via a CSV spreadsheet using Nutshell's field import tool, or manually recreate items in the settings. Tax‑rate logic tied to zip codes does not transfer and must be re‑established in your accounting or payment integration.

  • Custom form branching logic collapses in Nutshell

    Trade Service Pro custom forms support conditional field visibility and multi-step branching. Nutshell custom fields are simple — picklist, text, number, date, checkbox — with no conditional display logic. Multi-step intake forms migrate field by field, so the original branching flow is lost during the transfer. FlitStack extracts the full form schema and includes a dependency map in the migration plan, showing which fields were conditionally shown and on what values. Your Nutshell admin can use this map to rebuild the most critical branching rules using Nutshell's form builder and optional third‑party form tools that support conditional logic.

  • Credit card processing data does not transfer

    Trade Service Pro's integrated payment processing stores transaction IDs, payment method tokens, and gateway references that are not portable across payment processors. FlitStack migrates invoice records but does not transfer the underlying payment transaction history, because tokenized data cannot be recreated in a new gateway environment. Before decommissioning Trade Service Pro, export all transaction records from the payment gateway dashboard as CSV or via API, preserving fields such as transaction ID, amount, date, and payment method. These exports allow your accounting team to reconcile historical payments in your new accounting or payment tool. Nutshell itself does not store payment data, so payment reconciliation must occur outside the CRM.

Migration approach

Six steps for a successful Trade Service Pro to Nutshell data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

Trade Service Pro logo

Trade Service Pro

Source

Strengths

  • All-in-one FSM bundle covering CRM, proposals, invoicing, and scheduling for trade contractors.
  • Month-to-month subscription with no annual contract commitment.
  • 30-day free trial with no credit card required for sign-up.
  • Integrated payment processing marketed as accelerating collections for field service businesses.
  • User permission controls differentiate back-office and field technician access levels.

Weaknesses

  • No public API documented, preventing automated integrations or programmatic data exports.
  • No published pricing tiers on the website; cost transparency requires a sales conversation.
  • Small company footprint (11–50 employees, <$5M revenue) suggests limited enterprise-scale features.
  • Support is ticket-based with no documented SLA, leading to unpredictable response times.
  • Schema is undocumented; custom fields and object relationships are not publicly described.
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Trade Service Pro and Nutshell.

  • Object compatibility

    B

    1 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Trade Service Pro: Not publicly documented.

  • Data volume sensitivity

    B

    Trade Service Pro doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Trade Service Pro to Nutshell migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Trade Service Pro to Nutshell data migrations

Answers to the questions buyers ask most during Trade Service Pro to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most Trade Service Pro to Nutshell migrations complete in 24–72 hours for under 10,000 total records. Migrations with 50,000+ records, extensive job history, or multiple custom form schemas extend to 5–10 business days. The sample migration and validation phase adds 1–2 days upfront but prevents errors during the full run. Trade Service Pro's platform shutdown adds urgency — FlitStack can accelerate scoping for teams with imminent deadlines.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Trade Service Pro.
Land in Nutshell, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day