CRM migration
Field-level mapping, validation, and rollback between Kickserv and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Kickserv
Source
Nutshell
Destination
Compatibility
15 of 15
objects map 1:1 between Kickserv and Nutshell.
Complexity
BStandard
Timeline
24–48 hours
Overview
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.
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 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
Nutshell
Person
1:1Kickserv 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
Nutshell
Company
1:1Kickserv 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
Nutshell
Person
1:1Kickserv 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
Nutshell
Deal
1:1Kickserv 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
Nutshell
Deal Stage (Pipeline)
1:1Kickserv'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
Nutshell
Deal Activity (Note)
1:1Kickserv 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
Nutshell
Deal (Amount field)
1:1Kickserv 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)
Nutshell
Custom Field (Deal)
1:1Kickserv 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)
Nutshell
Custom Field (Person / Company)
1:1Kickserv 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
Nutshell
Activity (Note)
1:1Kickserv 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
Nutshell
Activity (Call / Meeting)
1:1Kickserv 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
Nutshell
Note
1:1Kickserv 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
Nutshell
User
1:1Kickserv 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
Nutshell
No Equivalent
1:1Kickserv 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
Nutshell
Custom Field (Deal)
1:1Kickserv 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.
| Kickserv | Nutshell | Compatibility | |
|---|---|---|---|
| Customer | Person1:1 | Fully supported | |
| Customer Address | Company1:1 | Fully supported | |
| Contact | Person1:1 | Fully supported | |
| Job | Deal1:1 | Fully supported | |
| Job Status | Deal Stage (Pipeline)1:1 | Fully supported | |
| Estimate | Deal Activity (Note)1:1 | Fully supported | |
| Invoice | Deal (Amount field)1:1 | Fully supported | |
| Custom Field (Job-level) | Custom Field (Deal)1:1 | Fully supported | |
| Custom Field (Customer-level) | Custom Field (Person / Company)1:1 | Fully supported | |
| Time Entry | Activity (Note)1:1 | Fully supported | |
| Event | Activity (Call / Meeting)1:1 | Fully supported | |
| Note | Note1:1 | Fully supported | |
| Employee | User1:1 | Fully supported | |
| GPS Check-in | No Equivalent1:1 | Fully supported | |
| Service / Service Template | Custom Field (Deal)1: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.
Kickserv gotchas
No offline mode breaks field work in dead zones
API access gated behind Premium plan tier
QuickBooks sync errors corrupt data if not resolved pre-migration
20-user hard cap forces complete platform switch
API token resets on password change
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
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.
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.
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.
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.
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
Kickserv
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 Kickserv 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
Kickserv: Not publicly documented.
Data volume sensitivity
Kickserv 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 Kickserv to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Kickserv 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 Kickserv
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.