CRM migration
Field-level mapping, validation, and rollback between Service In Sync and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Service In Sync
Source
Nutshell
Destination
Compatibility
10 of 10
objects map 1:1 between Service In Sync and Nutshell.
Complexity
BStandard
Timeline
24–72 hours
Overview
Service In Sync is a field-service operations platform built for scheduling jobs, managing estimates, processing payments, and collecting reviews — it treats clients and service records as first-class objects within a single operational system. Nutshell is a sales CRM that separates People, Companies, Leads, and Deals into a structured relationship graph, with pipelines, activities, and custom fields configured separately from the data layer. The migration requires mapping SIS's client records to Nutshell Companies (with primary contacts as People), service/job history to Notes and Activities on the relevant Company or Person, estimates to Nutshell Deals, and any custom fields on SIS clients to Nutshell custom fields on the corresponding object. Nutshell's JSON-RPC API exposes Contacts and Accounts as 'entities' with relationship 'maps' — FlitStack AI reads SIS data via its export interface, transforms records to match Nutshell's entity structure, and upserts through the API with owner resolution by email. Workflows, automations, and payment-processing logic do not transfer and must be rebuilt in Nutshell's automation layer. A delta-pickup window captures any SIS changes during the cutover before the destination is finalized.
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 Service In Sync 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.
Service In Sync
Client
Nutshell
Company (Account)
1:1Service In Sync clients map directly to Nutshell Companies. The client name becomes the Company name, domain/website maps to the Company website field, and any custom fields on the client record migrate as Nutshell custom fields on the Company object. Primary contact information is extracted separately for mapping to the Person record.
Service In Sync
Client Contact
Nutshell
Person (Contact)
1:1Primary contacts associated with SIS clients migrate to Nutshell People. The contact's name, email, phone, and job title map to the corresponding Nutshell Person fields. The relationship between the Person and the Company (Account) is established via Nutshell's relationship map. Secondary contacts on the same SIS client create additional Person records linked to the same Company.
Service In Sync
Job / Service Record
Nutshell
Activity / Note on Company or Person
1:1Service In Sync job records contain job description, status, scheduled date, assigned staff, and completion notes. We extract the job narrative as a Nutshell Note attached to the relevant Company record, preserving the original job date as the Note creation timestamp. Staff names are stored as text within the Note body since Nutshell does not have a native staff object.
Service In Sync
Estimate
Nutshell
Deal (Opportunity)
1:1SIS estimates with line items, totals, approval status, and signatures map to Nutshell Deals. The estimate total becomes the Deal amount, the description maps to the Deal name, and approval status is stored as a custom pick-list field on the Deal. Line-item detail is preserved as a Note attached to the Deal record.
Service In Sync
Payment / Deposit Record
Nutshell
Custom Fields / Note on Deal or Company
1:1Payment amounts, dates, and methods from SIS migrate as custom fields on the associated Deal or Company record. Nutshell does not have a native payment object, so billing history is preserved for reference in custom fields or as a structured Note. Actual payment processing must be handled by a separate billing tool post-migration.
Service In Sync
Review Request Record
Nutshell
Custom Fields on Company or Person
1:1SIS tracks review status, platform (Google, Yelp, Facebook), and request date per client. This data migrates as custom fields on the corresponding Nutshell Company or Person record (Review_Status__c, Review_Platform__c, Review_Request_Date__c) for reference. Nutshell does not have native review-tracking functionality. The custom fields preserve review history for reference and allow your team to maintain visibility into client feedback without manual re-entry.
Service In Sync
Lead
Nutshell
Lead
1:1Prospective clients entered directly in SIS as leads map 1:1 to Nutshell Leads. The lead name, contact information, source, and any custom fields transfer directly. Pipeline stage is not applicable in SIS for leads, so they land in Nutshell's default Lead status and can be re-staged during the migration review.
Service In Sync
Staff / Technician
Nutshell
User (Nutshell Owner)
1:1Service In Sync staff profiles (technicians, dispatchers) do not have a direct equivalent in Nutshell's CRM model. Nutshell Users are CRM owners and salespeople, not field technicians. Staff records are not migrated; instead, owner assignment in Nutshell is resolved by matching SIS staff email addresses to Nutshell User accounts, or flagged for manual assignment.
Service In Sync
Custom Fields on Client / Contact / Job
Nutshell
Custom Fields on Company / Person / Lead / Deal
1:1Any custom properties configured in SIS on clients, contacts, or jobs are created as custom fields in Nutshell on the corresponding target object. SIS custom field types (text, number, date, pick-list) are matched to Nutshell's supported custom field types. Pick-list fields in SIS require value-by-value mapping to Nutshell pick-list options.
Service In Sync
File Attachments (on Job / Estimate)
Nutshell
Note Attachments on Company, Person, or Deal
1:1Files attached to SIS jobs or estimates (photos, signed documents, invoices) are extracted and re-uploaded as Note attachments in Nutshell, linked to the corresponding Company, Person, or Deal record. File size limits follow Nutshell's attachment constraints. Large files may require compression before upload, and any files exceeding Nutshell's size limits will be flagged for manual handling or alternative storage solutions.
| Service In Sync | Nutshell | Compatibility | |
|---|---|---|---|
| Client | Company (Account)1:1 | Fully supported | |
| Client Contact | Person (Contact)1:1 | Fully supported | |
| Job / Service Record | Activity / Note on Company or Person1:1 | Fully supported | |
| Estimate | Deal (Opportunity)1:1 | Fully supported | |
| Payment / Deposit Record | Custom Fields / Note on Deal or Company1:1 | Fully supported | |
| Review Request Record | Custom Fields on Company or Person1:1 | Fully supported | |
| Lead | Lead1:1 | Fully supported | |
| Staff / Technician | User (Nutshell Owner)1:1 | Fully supported | |
| Custom Fields on Client / Contact / Job | Custom Fields on Company / Person / Lead / Deal1:1 | Fully supported | |
| File Attachments (on Job / Estimate) | Note Attachments on Company, Person, or Deal1: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.
Service In Sync gotchas
No public API documentation found
Automation rules do not export as data
Review data is partial — ratings live off-platform
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 Service In Sync data export and map to Nutshell schema
We extract a full export of your Service In Sync data including clients, contacts, jobs, estimates, payments, reviews, and all custom fields. We then audit the export against Nutshell's entity model — mapping each SIS object type to its corresponding Nutshell object (Company, Person, Lead, Deal) and identifying any custom fields that must be pre-created in Nutshell. The output is a field-level mapping document and a custom field creation checklist delivered for your Nutshell admin to execute before migration.
Create Nutshell custom fields and resolve user accounts
Based on the mapping audit, we identify every SIS custom property that requires a Nutshell custom field and provide step-by-step instructions for your Nutshell admin to create them. Simultaneously, we resolve owner assignment by matching SIS staff email addresses to existing Nutshell User accounts — any unmatched staff are flagged for your team to create Nutshell users or assign a fallback owner before the migration run. No data migrates until all custom fields exist and owner resolution is confirmed.
Run a sample migration with field-level diff
We migrate a representative slice of your SIS data — typically 100–500 records spanning clients, contacts, jobs, estimates, and leads — and generate a field-level diff comparing the source values against what landed in Nutshell. You review the sample in Nutshell to verify that client names, contact links, estimate amounts, and job Notes appear correctly. Any mapping adjustments are documented and applied before the full migration commits.
Execute full migration with delta-pickup window
The full migration runs against your Nutshell instance via the Nutshell JSON-RPC API, migrating all confirmed records in the sequence defined by object dependencies (Companies before People, Leads and Deals after their linked entities exist). A delta-pickup window of 24–48 hours captures any new or modified records in SIS that were created during the migration run. All operations are logged in an audit trail, and one-click rollback is available if reconciliation identifies missing or mis-mapped records.
Deliver reconciliation report and rebuild reference exports
Post-migration, we deliver a reconciliation report comparing record counts and field totals between SIS and Nutshell. We also export your SIS workflow definitions, automation rules, and payment-processing setup as reference documents for your team to use when rebuilding those capabilities in Nutshell or a separate tool. Custom field coverage, file attachment counts, and Notes attached to each record are included in the final handoff summary.
Platform deep dives
Service In Sync
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 Service In Sync 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
Service In Sync: Not publicly documented.
Data volume sensitivity
Service In Sync 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 Service In Sync to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Service In Sync 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 Service In Sync
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.