CRM migration
Field-level mapping, validation, and rollback between Fieldmagic and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Fieldmagic
Source
Nutshell
Destination
Compatibility
14 of 14
objects map 1:1 between Fieldmagic and Nutshell.
Complexity
BStandard
Timeline
3–5 days
Overview
Fieldmagic organizes data around field-service operations: Customers (billing entities), Sites (service locations), Contacts (individuals at those locations), Jobs (the core work record with status, assigned technician, schedule, and line items), Quotes (proposals linked to customers), and Assets (equipment tracked at sites with maintenance history). Custom fields, checklists, and job attachments add business-specific depth. Nutshell, by contrast, is a sales CRM that centers on People, Companies, Leads, and Deals (called Opportunities in some CRM contexts). Nutshell has no native job or asset concept — these must be reconstructed using Deals, custom fields, and Notes. The migration therefore involves a structural inversion: Fieldmagic's operational records become Nutshell's commercial records. FlitStack AI extracts Fieldmagic data via its REST API using scoped read access, transforms job records into Deals with custom fields carrying job-type, status, and site references, maps Fieldmagic customers to Nutshell Companies with site data stored as custom fields on each Company record, and preserves asset records as Nutshell custom fields or linked Notes with serial numbers and service history. Fieldmagic workflows — including auto-scheduling rules, trigger conditions, and escalation logic — do not migrate and must be rebuilt in Nutshell's automation tools. Quoting templates and pricing rules from Fieldmagic carry over as reference data only.
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 Fieldmagic 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.
Fieldmagic
Customer
Nutshell
Company
1:1Fieldmagic Customers map directly to Nutshell Companies. Both represent the billing entity — the organization you invoice and manage contracts against. Customer name, phone, billing address, and tax ID transfer as Company fields. Fieldmagic's per-customer notes and credit terms map to custom fields on the Nutshell Company record.
Fieldmagic
Contact
Nutshell
Person
1:1Fieldmagic Contacts map to Nutshell People — individuals linked to a Company. Email, phone, mobile, job title, and role at site transfer as Person fields. Fieldmagic's Contact type (e.g., Primary, Site Manager) maps to a custom pick-list field (Contact_Role__c) on the Person record.
Fieldmagic
Site
Nutshell
Custom Fields on Company
1:1Fieldmagic Sites have no native Nutshell equivalent — Nutshell has no location object. Each Site becomes a set of custom fields on the associated Company: Site_Name__c, Site_Address__c, Site_Access_Notes__c, and Site_Primary_Contact__c linking to the relevant Person. For multi-site customers, each Site generates a separate Company record with a Parent_Company__c custom field linking back to the primary Company.
Fieldmagic
Job
Nutshell
Deal
1:1Fieldmagic Jobs are the core record — they link Customer, Site, assigned technician, schedule window, status, line items, and attachments. Each Job maps to a Nutshell Deal with Job_Number__c, Job_Type__c, Job_Status__c, Assigned_Technician__c, Scheduled_Start__c, and Scheduled_End__c stored as custom fields. The Deal's monetary value maps from the Job's total invoice amount or quoted value.
Fieldmagic
Job Status
Nutshell
Deal Stage
1:1Fieldmagic job statuses (Booked, In Progress, On Hold, Completed, Invoiced, Cancelled) map to Nutshell Deal stages via value-by-value mapping. 'Completed' and 'Invoiced' both map to Won; 'Cancelled' maps to Lost; active statuses map to pipeline stages your team configures in Nutshell before migration.
Fieldmagic
Quote
Nutshell
Deal (unconverted)
1:1Fieldmagic Quotes are proposals linked to a Customer with line items, pricing, and validity dates. Each Quote becomes a Nutshell Deal in a 'Proposal' stage with Quote_Number__c, Quote_Valid_Until__c, and line-item summary stored as custom fields. Full quote PDF attachments are re-uploaded to Nutshell Files and linked to the Deal record.
Fieldmagic
Asset Type
Nutshell
Custom Object or Custom Fields
1:1Fieldmagic Asset Types define categories of equipment (e.g., HVAC Unit, Elevator, Generator) with associated maintenance checklists. Asset Type names migrate as a custom pick-list field (Asset_Type__c) on a Nutshell custom object or as structured custom fields on the linked Company/Site record.
Fieldmagic
Asset
Nutshell
Custom Object: Fieldmagic_Asset__c
1:1Each Fieldmagic Asset — with serial number, install date, make/model, warranty expiry, and linked Site — becomes a record in a Nutshell custom object (Fieldmagic_Asset__c) linked to the relevant Company via a lookup field. Maintenance history from Asset Service Records maps to a related Notes section on each Asset record.
Fieldmagic
Job Line Item
Nutshell
Custom Fields on Deal
1:1Fieldmagic Job line items (labor, materials, sublet) cannot map to native Nutshell fields since Nutshell has no line-item model. A summary of line-item categories and totals (e.g., 'Labor: $450, Materials: $120') is stored in a custom text area field (Job_Line_Items_Summary__c) on the Deal record. Individual line-item detail is preserved in a linked Nutshell Note.
Fieldmagic
Contract / Pricing Agreement
Nutshell
Custom Fields + Note on Company
1:1Fieldmagic contract pricing agreements (recurring billing rates,discount schedules) have no Nutshell equivalent. Contract terms and rates are stored in a custom field (Contract_Terms__c) and a linked Note on the Company record. Rebuilt pricing rules can be documented from this reference.
Fieldmagic
Attachment / Document
Nutshell
Nutshell Files
1:1Fieldmagic file attachments on Jobs, Quotes, and Customers (photos, signed forms, invoices) are downloaded and re-uploaded to Nutshell Files linked to the corresponding Deal or Company record. Nutshell's file size limit (25 MB per file) applies; large files are flagged before migration.
Fieldmagic
Technician / Office User
Nutshell
Nutshell User (by email match)
1:1Fieldmagic technicians and office users are resolved to Nutshell Users by matching email addresses. Unmatched users are flagged before migration — teams either create Nutshell user accounts for them or assign their records to a fallback Nutshell user. Nutshell does not have a field-technician scheduling model, so this mapping is for owner/reporter attribution only.
Fieldmagic
Activity History (calls, emails, site visits logged in Jobs)
Nutshell
Activity on Deal
1:1Fieldmagic job-level activity notes (site visit summaries, technician comments, customer communications logged in the job) are extracted as Activity records and linked to the corresponding Nutshell Deal. Original timestamps and author are preserved. Nutshell's Activity model supports notes, calls, and emails on Deals.
Fieldmagic
Checklist (on Job or Asset)
Nutshell
Note on Deal or Custom Object
1:1Fieldmagic checklists attached to Jobs or Assets (safety items, inspection steps, service requirements) have no Nutshell structural equivalent. Checklist content is preserved as a formatted Note attached to the relevant Deal or Asset record. The checklist structure — ordered steps with pass/fail status — is stored as plain text for manual rebuild reference.
| Fieldmagic | Nutshell | Compatibility | |
|---|---|---|---|
| Customer | Company1:1 | Fully supported | |
| Contact | Person1:1 | Fully supported | |
| Site | Custom Fields on Company1:1 | Fully supported | |
| Job | Deal1:1 | Fully supported | |
| Job Status | Deal Stage1:1 | Fully supported | |
| Quote | Deal (unconverted)1:1 | Fully supported | |
| Asset Type | Custom Object or Custom Fields1:1 | Fully supported | |
| Asset | Custom Object: Fieldmagic_Asset__c1:1 | Fully supported | |
| Job Line Item | Custom Fields on Deal1:1 | Fully supported | |
| Contract / Pricing Agreement | Custom Fields + Note on Company1:1 | Fully supported | |
| Attachment / Document | Nutshell Files1:1 | Fully supported | |
| Technician / Office User | Nutshell User (by email match)1:1 | Fully supported | |
| Activity History (calls, emails, site visits logged in Jobs) | Activity on Deal1:1 | Fully supported | |
| Checklist (on Job or Asset) | Note on Deal or Custom Object1: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.
Fieldmagic gotchas
Site-Asset hierarchy is a mandatory import dependency
Checklist auto-attachment and completion data require separate handling
Salesforce custom objects and custom fields are not covered by standard import
Contract pricing links to invoicing require value-level mapping
Bulk API extraction is not publicly documented
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 Fieldmagic data structure and Nutshell destination schema
FlitStack AI connects to Fieldmagic via its REST API using scoped read access and inventories all Customers, Contacts, Sites, Jobs, Quotes, Assets, and custom fields. In parallel, we survey your Nutshell account to confirm existing custom objects, Deal stages, and pick-list values. This audit produces a preliminary field-mapping spreadsheet and flags blockers — missing Nutshell custom objects, unconfigured Deal stages, or Fieldmagic custom fields without a clear destination — before any migration work begins.
Design and provision Nutshell custom objects and fields
Based on the audit, FlitStack AI creates the Fieldmagic_Asset__c custom object (with all mapped asset fields), creates custom fields on the Deal object (Job_Number__c, Job_Type__c, Job_Status__c, Scheduled_Start__c, Scheduled_End__c, Assigned_Technician__c, Invoice_Status__c, Site_Reference__c, Original_Create_Date__c), creates custom fields on the Company object for site data (Site_Name__c, Site_Address__c, Site_Access_Notes__c, Parent_Company__c), and creates custom fields on the Person object (Contact_Role__c). Your Nutshell admin approves the field list before we proceed. This step is the longest planning phase in a Fieldmagic-to-Nutshell migration because of the structural gap between a field-service data model and a CRM data model.
Configure Deal stages and value mapping
Your Nutshell admin creates Deal pipeline stages that correspond to Fieldmagic job statuses. FlitStack AI provides a value-mapping template mapping each Fieldmagic status (Booked, In Progress, On Hold, Completed, Invoiced, Cancelled) to a specific Nutshell stage. Probability and forecast-category values are assigned per stage. We also map Fieldmagic quote statuses to separate Deal stages so historical quotes and active jobs live in distinct pipeline views.
Run sample migration with field-level diff
A representative slice — typically 100–300 records spanning Customers, Contacts, Sites, Jobs, Quotes, and Assets — migrates into Nutshell in a test pass. FlitStack AI generates a field-level diff report comparing each source field value against the destination field value, confirming that custom fields populated correctly, Deal stages resolved, and asset records linked to the right Company. You review the diff with your team and request corrections to the mapping before the full run commits.
Execute full migration with delta-pickup window
The full dataset migrates into Nutshell using the approved mapping. During the cutover window — typically 24–48 hours — FlitStack AI captures any new or modified Fieldmagic records (new jobs created, status changes, updated customer data) and applies them to Nutshell. All operations are logged in an audit trail. One-click rollback reverts Nutshell to its pre-migration state if reconciliation fails. After rollback confirmation, the final delta is applied and your team goes live on Nutshell.
Platform deep dives
Fieldmagic
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 Fieldmagic 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
Fieldmagic: Not publicly documented.
Data volume sensitivity
Fieldmagic 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 Fieldmagic to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Fieldmagic 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 Fieldmagic
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.