CRM migration

Migrate from Kickserv to Nutshell

Field-level mapping, validation, and rollback between Kickserv and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

Kickserv logo

Kickserv

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

15 of 15

objects map 1:1 between Kickserv and Nutshell.

Complexity

BStandard

Timeline

24–48 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Kickserv is a field-service management platform built around jobs, technicians, and dispatch — every record is anchored to a work order. Nutshell is a sales CRM built around people, companies, and deals — records are anchored to contacts and pipelines. The migration requires translating Kickserv's job-centric data model into Nutshell's contact-centric model without losing service history, customer records, or custom field data. We extract Kickserv data via its REST API (Basic Auth with employee tokens, available on Premium plan), mapping customers to Nutshell People, jobs to Nutshell Deals with pipeline stages reflecting job status, and invoices to deal-level financial records. Custom fields on Kickserv jobs and customers become Nutshell custom fields on People, Leads, and Deals. Time entries, notes, and attachments surface as activities or notes in Nutshell. GPS check-in history and dispatch maps have no Nutshell equivalent and are flagged for manual reference. Workflows, sequences, automations, and QuickBooks sync configurations do not migrate — they require rebuild in Nutshell or reconfiguration in QuickBooks. Our team sequences the migration so foreign-key relationships (customer-to-job, employee-to-job) resolve correctly, then runs a sample migration with field-level diff before committing the full cutover.

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

Kickserv logo

Kickserv

What's pushing teams away

  • Mobile app glitches frequently with white screen freezes, clock-in failures, and lag that disrupts technicians working in the field.
  • Hard 20-user ceiling forces growing companies to find an entirely new platform, with no path to higher user counts within Kickserv itself.
  • No offline mode means technicians in basements, rural properties, or dead zones lose access to their job data mid-assignment.
  • Page load performance in the web app is slow, frustrating office staff who rely on the dashboard for daily dispatching tasks.
  • QuickBooks Desktop integration requires an extra $50/month add-on fee that is not obvious at purchase time.

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 Kickserv objects map to Nutshell

Each row shows how a Kickserv 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.

Kickserv

Customer

maps to

Nutshell

Person

1:1
Fully supported

Kickserv customers map directly to Nutshell People. The customer's name splits into Nutshell's firstName and lastName fields. A customer may have multiple contacts (technicians, office staff) — each contact becomes a separate Nutshell Person record linked to the same Company.

Kickserv

Customer Address

maps to

Nutshell

Company

1:1
Fully supported

Kickserv stores a single address per customer record. When a customer has both a billing and service address, the service address (job location) is preserved as a custom field on the Nutshell Company. Nutshell's Company object holds the primary address; job-site addresses are flagged for manual review.

Kickserv

Contact

maps to

Nutshell

Person

1:1
Fully supported

Kickserv contact records (individuals linked to a customer) map to Nutshell People. Email, phone, and role fields transfer directly. Contacts without an email address are flagged — Nutshell requires an email for People records, so these may route to Leads or require manual enrichment.

Kickserv

Job

maps to

Nutshell

Deal

1:1
Fully supported

Kickserv jobs are the central record type and map to Nutshell Deals. The job's status (Scheduled, In Progress, Completed, On Hold) becomes a Nutshell pipeline stage value. Job service type determines which Nutshell pipeline receives the record. The job description and internal notes become the Deal description.

Kickserv

Job Status

maps to

Nutshell

Deal Stage (Pipeline)

1:1
Fully supported

Kickserv's four job statuses are mapped to Nutshell pipeline stages by service type. 'Scheduled' and 'In Progress' map to open pipeline stages; 'Completed' maps to a closed-won stage; 'On Hold' maps to a stalled or needs-action stage. Each mapping is value-by-value per pipeline.

Kickserv

Estimate

maps to

Nutshell

Deal Activity (Note)

1:1
Fully supported

Kickserv estimates (line items, quantities, pricing) map to Nutshell Deal activities. The estimate total and status (sent, approved, declined) are stored as custom fields on the Deal. Approved estimates that converted to jobs are linked to the resulting Deal record.

Kickserv

Invoice

maps to

Nutshell

Deal (Amount field)

1:1
Fully supported

Kickserv invoices carry an amount, status (paid, unpaid, overdue), and payment date. The invoice amount maps to the Nutshell Deal Amount field. Invoice status is preserved as a custom pick-list field on the Deal. Paid invoices also create a Note activity recording the payment event.

Kickserv

Custom Field (Job-level)

maps to

Nutshell

Custom Field (Deal)

1:1
Fully supported

Kickserv custom fields attached to Jobs require Nutshell custom fields on the Deal object. We create Nutshell custom fields with matching types (text, number, date, pick-list) before migration. Service-type-filtered custom fields are preserved as standard Deal custom fields — filtering logic is noted for manual rebuild in Nutshell views.

Kickserv

Custom Field (Customer-level)

maps to

Nutshell

Custom Field (Person / Company)

1:1
Fully supported

Kickserv customer custom fields (such as tax ID, trade license number, or preferred contact method) become Nutshell Person or Company custom fields. We match the field type and preserve all existing values. Fields with no value in Kickserv are left blank in Nutshell.

Kickserv

Time Entry

maps to

Nutshell

Activity (Note)

1:1
Fully supported

Kickserv time entries record hours worked per employee per job. These map to Nutshell Note activities attached to the Deal, noting the employee name, date, and hours logged. Nutshell has no native time-tracking field — this is a reference-only mapping.

Kickserv

Event

maps to

Nutshell

Activity (Call / Meeting)

1:1
Fully supported

Kickserv events such as appointments or scheduled site visits are converted into Nutshell Activities of type 'call' or 'meeting' depending on the event's assigned type field in Kickserv. The original start time, end time, duration, and the assigned employee are all transferred to the corresponding Nutshell activity, preserving the scheduling context for future reference.

Kickserv

Note

maps to

Nutshell

Note

1:1
Fully supported

Kickserv notes attached to jobs, customers, or contacts map to Nutshell Notes linked to the equivalent record. Rich-text formatting is preserved where Kickserv supports it. Notes without a parent record are attached to the most logically related Deal or Person.

Kickserv

Employee

maps to

Nutshell

User

1:1
Fully supported

Kickserv employees (technicians, dispatchers) are matched to Nutshell users by email address. Unmatched employees are flagged — Nutshell requires a user account for activity assignment. Owner resolution happens before the migration run so all records land with a valid Nutshell user.

Kickserv

GPS Check-in

maps to

Nutshell

No Equivalent

1:1
Fully supported

Kickserv GPS check-ins record technician location at job start and end. Nutshell has no location-tracking field on any object. We flag GPS data for export as a CSV reference file — it must be reviewed manually in Nutshell if location context is required.

Kickserv

Service / Service Template

maps to

Nutshell

Custom Field (Deal)

1:1
Fully supported

Kickserv service types (the type of work performed, such as HVAC Repair or Plumbing) define job templates and custom field visibility. Nutshell has no service-type object. Service types are preserved as a Deal custom field so pipeline segmentation by service type is still possible.

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.

Kickserv logo

Kickserv gotchas

High

No offline mode breaks field work in dead zones

High

API access gated behind Premium plan tier

Medium

QuickBooks sync errors corrupt data if not resolved pre-migration

Medium

20-user hard cap forces complete platform switch

Low

API token resets on password change

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

  • Kickserv job status has no 1:1 Nutshell pipeline stage

    Kickserv uses four fixed job statuses (Scheduled, In Progress, Completed, On Hold) that apply across all service types. Nutshell pipeline stages are scoped per pipeline, and each pipeline can have its own set of stage names and probability weights. We map Kickserv statuses to Nutshell stage values per pipeline, but if a Kickserv setup uses service-type-specific status logic (such as a five-stage HVAC workflow), those intermediate stages cannot map directly — they collapse to the four Kickserv statuses, and the pipeline in Nutshell needs to be pre-configured to accommodate the source workflow.

  • GPS check-in and dispatch data cannot be represented in Nutshell

    Kickserv's GPS check-in records, dispatch grid view, and route-optimization data are field-service-specific constructs with no equivalent in Nutshell's data model. The GPS coordinates and timestamp of a technician arriving at a job site cannot be stored on a Nutshell Person or Deal record. We export this data as a CSV reference file during migration, but it cannot be displayed natively in Nutshell. Teams relying on GPS check-in data for billing or compliance purposes must rebuild that verification process using Nutshell's activity logging or a third-party integration.

  • Kickserv user cap creates urgency for post-migration user management

    The Kickserv 20-user ceiling means teams arriving at Nutshell are often actively scaling. The Nutshell Enterprise plan at $79/user/month requires explicit license management — unlike Kickserv's flat tiers where adding a user above the cap was impossible, Nutshell allows unlimited seats but bills per user. We flag records assigned to employees who are not yet Nutshell users so your team can create the accounts before go-live, avoiding records landing with an 'unassigned' owner.

  • Kickserv custom fields filtered by service type require manual rebuild of filtering logic

    Kickserv allows custom fields on Jobs to be filtered so they appear only for specific service types — for example, a 'refrigerant_type' field visible only on HVAC jobs. Nutshell custom fields on Deals do not support conditional visibility by field value. All migrated custom fields appear on every Deal regardless of service type. We create the fields and migrate all values; the conditional-display logic must be rebuilt in Nutshell using filtered views or list settings.

  • QuickBooks sync configuration does not migrate and must be rebuilt

    Kickserv's two-way sync with QuickBooks Online or Desktop — controlling which invoices push to QuickBooks, which payments pull back, and the sync interval — is a Kickserv-specific configuration that does not transfer to Nutshell. Nutshell lacks a native QuickBooks integration, so teams moving from Kickserv to Nutshell must set up the connection from scratch, map the same objects, and resolve any duplicate invoice records already present in both platforms. This rebuild effort should be planned during the migration to avoid post‑cutover reconciliation issues.

Migration approach

Six steps for a successful Kickserv to Nutshell data migration

  1. Scope Kickserv data and design Nutshell schema plan

    We connect to the Kickserv API using the account's employee token (Premium plan required for API access), enumerate all object types, and count records by type. We identify custom fields on Jobs and Customers, note service-type filtering rules, and audit which employees are active users versus inactive. We then deliver a Nutshell schema plan: which pipelines to create, which stage values to map per Kickserv job status, and which custom fields to pre-create on Person, Company, and Deal objects. The schema plan is reviewed by your team before any data moves.

  2. Match Kickserv employees to Nutshell users by email

    Kickserv employees (technicians, dispatchers, office staff) are matched to Nutshell user accounts by email address. We generate a match report showing which Kickserv employees have a corresponding Nutshell user, which do not, and which have multiple matches. Your team creates missing Nutshell user accounts before migration so all Deal records land with a valid owner. Records assigned to employees with no Nutshell user are flagged and assigned to a designated fallback owner.

  3. Run sample migration with field-level diff

    A representative slice of Kickserv data — typically 100–300 records spanning customers, contacts, jobs, invoices, and a few activities — migrates to Nutshell in a test pass. We generate a field-level diff comparing source values against destination field values so you can verify that job status-to-pipeline-stage mapping, custom field values, and owner resolution are correct. Any mapping adjustments are made before the full run. This step typically runs within 4–8 hours of clock time.

  4. Execute full migration with delta-pickup window

    The full Kickserv dataset migrates to Nutshell in dependency order: Companies first, then People, then Deals with stage mapping and custom field values populated. Activities (calls, meetings, notes, time entries) attach to the correct parent record. After the initial run, a delta-pickup window of 24–48 hours captures any records modified or created in Kickserv during the cutover. Your team continues working in Kickserv throughout this window — FlitStack uses scoped read access only.

  5. Validate, reconcile, and confirm rollback availability

    We validate record counts between Kickserv and Nutshell for each object type and spot-check field values across the migrated dataset. GPS check-in data, QuickBooks sync configuration, and service-type filtering logic are delivered as separate reference exports with a rebuild guide. An audit log records every operation. One-click rollback is available for 48 hours post-migration if reconciliation reveals systematic issues that require restarting the cutover.

Platform deep dives

Context on both ends of the pair

Kickserv logo

Kickserv

Source

Strengths

  • All-in-one FSM including scheduling, dispatch, invoicing, and GPS tracking with no feature gating across tiers.
  • Bidirectional QuickBooks Online sync is Gold Developer certified by Intuit and handles customers, invoices, and payments.
  • Per-user flat pricing with no per-job or per-transaction fees that can surprise smaller operators.
  • Custom templates for estimates, invoices, and work orders using Liquid templating are fully supported.
  • Full account data export is available from the Account & Billing settings section.

Weaknesses

  • Mobile app suffers from frequent glitches, white screen freezes, and clock-in failures that disrupt field operations.
  • No offline access means technicians lose all functionality when network connectivity drops.
  • Hard user cap of 20 across all plans with no enterprise tier or unlimited option for growth.
  • API uses XML over HTTP rather than JSON, limiting tool compatibility and requiring transformation during migration.
  • Rate limits and bulk export endpoints are not publicly documented, making migration scoping imprecise.
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. 2 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 Kickserv and Nutshell.

  • Object compatibility

    B

    2 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

    Kickserv: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

Estimate your Kickserv 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 Kickserv to Nutshell data migrations

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

Can't find your answer?

Walk through your Kickserv to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most Kickserv-to-Nutshell migrations complete in 24–48 hours for under 5,000 Kickserv records. Larger setups with 20,000+ records or more than 30 custom fields extend to 3–5 days. The longest planning step is designing the Nutshell pipeline schema — deciding how many pipelines to create and how Kickserv job statuses map to Nutshell stage values. The sample migration with field-level diff typically runs within 4–8 hours of scope confirmation.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Kickserv.
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