CRM migration

Migrate from Fieldmagic to Nutshell

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

Fieldmagic logo

Fieldmagic

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

14 of 14

objects map 1:1 between Fieldmagic and Nutshell.

Complexity

BStandard

Timeline

3–5 days

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Fieldmagic logo

Fieldmagic

What's pushing teams away

  • The platform becomes cost-prohibitive as teams scale — multiple office users, more technicians, and advanced features tier out quickly, and the per-seat model compounds for growing field service businesses.
  • Salesforce underpinnings add unnecessary complexity for straightforward field service needs — smaller teams report the CRM features feel oversized for their actual job management requirements.
  • Limited API documentation and no publicly documented bulk export mechanism makes it difficult for technical teams to build custom integrations or extract data for migration without vendor involvement.
  • Some users report the UI, while functional, lacks the polish of newer FSM competitors, and certain workflow automation features require a steeper learning curve to configure effectively.

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

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

maps to

Nutshell

Company

1:1
Fully supported

Fieldmagic 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

maps to

Nutshell

Person

1:1
Fully supported

Fieldmagic 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

maps to

Nutshell

Custom Fields on Company

1:1
Fully supported

Fieldmagic 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

maps to

Nutshell

Deal

1:1
Fully supported

Fieldmagic 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

maps to

Nutshell

Deal Stage

1:1
Fully supported

Fieldmagic 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

maps to

Nutshell

Deal (unconverted)

1:1
Fully supported

Fieldmagic 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

maps to

Nutshell

Custom Object or Custom Fields

1:1
Fully supported

Fieldmagic 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

maps to

Nutshell

Custom Object: Fieldmagic_Asset__c

1:1
Fully supported

Each 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

maps to

Nutshell

Custom Fields on Deal

1:1
Fully supported

Fieldmagic 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

maps to

Nutshell

Custom Fields + Note on Company

1:1
Fully supported

Fieldmagic 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

maps to

Nutshell

Nutshell Files

1:1
Fully supported

Fieldmagic 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

maps to

Nutshell

Nutshell User (by email match)

1:1
Fully supported

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

maps to

Nutshell

Activity on Deal

1:1
Fully supported

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

maps to

Nutshell

Note on Deal or Custom Object

1:1
Fully supported

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

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.

Fieldmagic logo

Fieldmagic gotchas

High

Site-Asset hierarchy is a mandatory import dependency

Medium

Checklist auto-attachment and completion data require separate handling

Medium

Salesforce custom objects and custom fields are not covered by standard import

Medium

Contract pricing links to invoicing require value-level mapping

High

Bulk API extraction is not publicly documented

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 site or location object, requiring multi-site customers to be restructured

    Fieldmagic's data model treats Sites as first-class objects linked to Customers — each site has its own address, access notes, and set of assets. Nutshell has no Sites concept; the closest structure is a Company record with custom fields. For Fieldmagic customers with multiple service locations, we either create one Company per site with a Parent_Company__c custom field linking back to the primary account, or we store all site data as custom fields on a single Company record. Either approach requires pre-migration schema design decisions, and your Nutshell admin should confirm the preferred structure before data lands. Teams that skip this step find their Nutshell reports grouped incorrectly by site.

  • Fieldmagic asset and maintenance records need a custom Nutshell object built before migration

    Nutshell has no Asset object. Fieldmagic's Asset Types and Assets — including serial numbers, install dates, warranty expiry dates, and service history — cannot map to any standard Nutshell field. FlitStack AI creates a Fieldmagic_Asset__c custom object in Nutshell with fields mirroring the source asset schema before migration runs. If your Nutshell plan limits custom objects or your team lacks admin access to create them, this step requires coordination. The custom object must be active and accessible to the migrating user before the full run commits, or asset records will fail to insert.

  • Job-to-Deal value mapping requires pre-migration stage configuration in Nutshell

    Fieldmagic job statuses (Booked, In Progress, On Hold, Completed, Invoiced, Cancelled) have no direct Nutshell equivalents — they must map to Deal stages your team has configured in Nutshell before migration. If your Nutshell account only has the default 'New Lead → Working → Proposal → Negotiation → Won/Lost' stages, jobs with status 'Booked' or 'Invoiced' will have nowhere to land. FlitStack AI delivers a stage-mapping plan during discovery; your Nutshell admin needs to create matching stages first. Stage mismatch is the most common reason for a migration hold during the validation step.

  • Fieldmagic checklists on jobs and assets cannot migrate as structured data

    Fieldmagic allows checklists to be attached to Jobs and Assets — ordered sets of inspection steps, safety items, or service tasks with pass/fail status. Nutshell has no checklist or survey object; there is no native way to represent ordered checklist steps. We preserve checklist content as plain-text Notes attached to the relevant Deal or Asset record. The ordering and pass/fail structure is lost — only the raw content survives. If your team relies on checklist data for compliance reporting or regulatory audits, this limitation must be acknowledged and the checklists rebuilt in Nutshell manually or via a third-party form tool after migration.

  • Fieldmagic technician scheduling and dispatch data has no Nutshell equivalent

    Fieldmagic's drag-and-drop scheduler manages technician assignments, availability windows, geographic routing, and skill-based dispatch. Nutshell has no scheduling, dispatch, or technician-capacity model — it is a sales CRM, not a field-service tool. We migrate the assigned technician name as a custom field on the Deal for historical reference, but the scheduling data (availability, travel time, skill match, route optimization) cannot be represented in Nutshell. Teams that rely on Fieldmagic's scheduling features should plan to either keep Fieldmagic for dispatch operations or evaluate dedicated FSM tools (such as ServiceTitan, Jobber, or UpKeep) post-migration.

Migration approach

Six steps for a successful Fieldmagic to Nutshell data migration

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

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

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

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

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

Context on both ends of the pair

Fieldmagic logo

Fieldmagic

Source

Strengths

  • End-to-end job lifecycle from quote through invoicing with time-and-materials and fixed-price billing in one platform.
  • Offline-capable mobile app with real-time GPS technician tracking and paperless field workflows.
  • Native Xero and QuickBooks Online accounting sync with MYOB AccountRight support for Australian businesses.
  • Built-in asset management with Site-level tracking, maintenance history, and inspection checklists.
  • All-inclusve pricing with no storage, usage, or basic support add-ons on any paid tier.

Weaknesses

  • Per-seat pricing compounds quickly as field teams grow — office user and mobile user licenses are counted separately.
  • Salesforce base adds CRM complexity that smaller field service teams may not need, increasing onboarding overhead.
  • Bulk API export mechanism is not publicly documented, limiting programmatic data extraction for migrations and integrations.
  • Mobile-only plan at $19/user/month lacks the full feature set available on higher tiers, creating feature-gated upgrades.
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 Fieldmagic 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

    Fieldmagic: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most Fieldmagic-to-Nutshell migrations complete in 3–5 days for under 25,000 total records. Larger setups with 100,000+ records, complex asset hierarchies, or multi-site customer structures extend to 10–18 days. The longest phase is typically the custom-object and custom-field provisioning step — designing the Nutshell schema to accommodate Fieldmagic's site and asset data takes 2–4 days of planning before any data moves. The actual API extraction and load runs in hours; the planning and validation determine the overall timeline.

Adjacent paths

Related migrations to explore

Ready when you are

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