CRM migration

Migrate from ServiceMax to Nutshell

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

ServiceMax logo

ServiceMax

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

12 of 12

objects map 1:1 between ServiceMax and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

ServiceMax organizes field service operations around Work Orders, Assets, Service Contracts, and Dispatch scheduling — a data model designed for technician dispatch, parts inventory, and SLA tracking. Nutshell models sales around People, Companies, Leads, and Deals with pipeline stages and activity tracking. These platforms share almost no object-level equivalences: ServiceMax's FSM primitives (Work Order Status, Dispatch Gantt, Preventive Maintenance, Entitlement) have no native counterpart in Nutshell. We map what we can — work order history as activity-linked Deals, assets as Companies with custom fields, service history as notes on the relevant contact or company record — and we are explicit about what cannot migrate because Nutshell's schema does not support it. ServiceMax configuration items (SFM Transactions, Wizards, Mobile Permissions) are FSM logic that belongs in a field-service platform, not a sales CRM, so those are excluded by design. The migration runs via Nutshell's JSON-RPC API with scoped read access on ServiceMax; your team continues working during cutover and a delta-pickup window captures any in-flight records.

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

ServiceMax logo

ServiceMax

What's pushing teams away

  • Enterprise customers report that total cost of ownership—licensing plus Salesforce admin resources plus implementation consultants—becomes prohibitive compared to standalone FSM platforms.
  • The steep configuration curve frustrates teams; one reviewer described it as 'a Lamborghini that takes a multitude of engineers to operate,' with heavy reliance on custom SFM Transactions and code.
  • Frequent Salesforce platform updates can break custom ServiceMax configurations, forcing re-testing and re-deployment of workflows, wizards, and mobile permissions after every major Salesforce release.
  • Organizations outgrow the product's reporting depth; multiple reviewers note limited visibility into attached files across Work Orders and difficulty building cross-object reports without dedicated BI tools.
  • Connectivity-dependent mobile apps cause productivity loss when technicians work in low-signal environments, and the browser mode lacks certain billing and pricing UI elements available in the native app.

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

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

ServiceMax

Work Order (SVMXC__Service_Order__c)

maps to

Nutshell

Deal

1:1
Fully supported

ServiceMax Work Orders map to Nutshell Deals as the primary migration object. The Work Order subject becomes the Deal name; Work Order status and priority map as custom fields. Original create date and last-modified date are preserved in custom datetime fields. Each Work Order's linked Contact becomes the Deal's primary Person.

ServiceMax

Work Order Line Item

maps to

Nutshell

Deal Line Item / Activity Note

1:1
Fully supported

Work Order Line Items—including parts consumed, labor hours, and service fees—are condensed into a structured text summary and attached as a note to the corresponding Nutshell Deal record. Each note captures the line item description, quantity, unit price, and total amount verbatim, preserving the complete financial history of the work performed. This approach maintains audit trail integrity while respecting Nutshell's native data model.

ServiceMax

Asset (SVMXC__Asset__c)

maps to

Nutshell

Company

1:1
Fully supported

ServiceMax Assets migrate as Nutshell Companies with a custom field identifying them as migrated assets. Asset serial number, install date, and status map to custom fields on the Company record. Account name uses the Asset's installed-at location or customer name depending on your specified rule.

ServiceMax

Contact (Contact)

maps to

Nutshell

Person

1:1
Fully supported

ServiceMax Contact records migrate directly to Nutshell People. First name, last name, email, phone, and title map 1:1. Owner resolution runs by email match against Nutshell users; unmatched owners are flagged before migration so you can assign them or invite them to Nutshell first.

ServiceMax

Account

maps to

Nutshell

Company

1:1
Fully supported

ServiceMax Account records representing customer organizations migrate directly to Nutshell Company records through field-to-field mapping. Standard fields including company name, website URL, industry classification, primary phone number, and complete billing address transfer to their Nutshell counterparts. Where ServiceMax captures multi-level parent Account hierarchies, Nutshell's single-parent Company model requires flattening—only the top-level parent relationship is preserved in the migration.

ServiceMax

Service Contract

maps to

Nutshell

Company custom fields

1:1
Fully supported

Service Contracts (SLAs, covered asset lists, renewable maintenance terms) have no Nutshell equivalent. We preserve contract name, start/end dates, and covered asset references as custom fields on the linked Nutshell Company record. Recurring billing logic must be rebuilt using Nutshell's integrations or a separate billing tool.

ServiceMax

Entitlement

maps to

Nutshell

Company custom fields

1:1
Fully supported

Entitlements define which SLAs apply to a specific asset or customer. We map entitlement name, service type, and response commitment as custom fields on the Nutshell Company or linked Asset-as-Company record. The SLA logic itself — response time rules, escalation paths — has no migration path and must be documented for manual rebuild.

ServiceMax

Preventive Maintenance Process

maps to

Nutshell

Activity (Task)

1:1
Fully supported

Preventive Maintenance records indicate scheduled service events. These migrate as Nutshell Tasks with the PM due date as the task due date, description from the PM record, and linked to the relevant Asset-as-Company. Recurring scheduling logic does not transfer — your team recreates recurring tasks in Nutshell manually or via a scheduling integration.

ServiceMax

Technician / Resource

maps to

Nutshell

Person

1:1
Fully supported

ServiceMax technician and resource records (users who perform field work) migrate as Nutshell People if they are also sales or customer-facing contacts. Internal-only dispatch resources that should not appear in Nutshell's CRM are excluded — your admin identifies the boundary before migration.

ServiceMax

Activity History (Calls, Emails, Logs)

maps to

Nutshell

Activity

1:1
Fully supported

ServiceMax activity records—including work order call logs, email correspondence, and general service history—migrate as Nutshell Activity entries linked to the appropriate Person or Deal record. The original creation timestamp, activity classification type, and descriptive content transfer intact to preserve the full service narrative. For customers with extensive activity histories, we leverage Nutshell's Bulk API capabilities to load high-volume records in optimized batches while maintaining data fidelity throughout the transfer process.

ServiceMax

Attachment / File

maps to

Nutshell

File attachment on Person or Deal

1:1
Fully supported

Files attached to Work Orders or Assets re-upload to Nutshell and attach to the corresponding Deal or Company record. File size limits and inline image handling follow Nutshell's attachment constraints. Large technical drawings or photos attached to Assets are included if your Nutshell plan supports the file size.

ServiceMax

SFM Transaction / SFM Wizard / Mobile Config

maps to

Nutshell

Not migratable

1:1
Fully supported

ServiceMax SFM Transactions, SFM Wizards, Technical Attributes, SPM Calculation Methods, and Mobile Configurations are FSM workflow constructs with no equivalent in Nutshell's sales CRM model. We export these definitions as a reference JSON bundle for your internal team or consultants to use when rebuilding equivalent automation logic in Nutshell.

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.

ServiceMax logo

ServiceMax gotchas

High

API call limits reset on a 24-hour rolling window

Medium

SFM Transaction and Wizard dependencies create migration loops

Medium

Configuration Profile migration excludes Default profiles

Low

Large Technical Attributes configurations slow the Migration Tool UI

Low

Pricing and Billing UI missing from browser mode

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

  • ServiceMax Work Order scheduling data has no destination counterpart

    ServiceMax models technician availability, travel time, skill requirements, and geographic dispatch as first-class data on the Work Order object. Nutshell has no scheduling model — Deals have due dates but no Gantt, no technician assignment, and no travel-time tracking. Dispatch assignments and scheduling windows stored in ServiceMax's SVMXC__Scheduled_Date__c and technician-link fields migrate as custom fields on Nutshell Deals, but the scheduling logic itself must be rebuilt in Nutshell using tasks and calendar integrations. If your ServiceMax instance relies heavily on dispatch optimization, be prepared to document the rules for a rebuild in Nutshell or a third-party scheduling tool.

  • FSM configuration items (SFM Transactions, Wizards, Technical Attributes) cannot migrate

    ServiceMax stores its workflow logic as SFM Transactions, SFM Wizards, Mobile Configurations, SPM Calculation Methods, and Technical Attribute templates. These are FSM-specific automation constructs that run on the Force.com platform and have no structural equivalent in Nutshell's JSON-RPC API. FlitStack AI exports the configuration bundle as a reference JSON file so your internal team or consulting partner can use it as a rebuild specification when designing equivalent Nutshell automation. However, the logic itself does not migrate and will need to be recreated manually.

  • Service Contract and Entitlement SLA data migrates as reference fields only

    ServiceMax Service Contracts define which assets are covered, the SLA response commitment (4-hour response, next-business-day resolution), and renewal terms. Nutshell has no contract object — these values can only exist as custom fields on the linked Company or Asset-as-Company record. The trigger logic that enforces SLA breach notifications in ServiceMax has no migration path. Your team must document the SLA terms and implement any automated enforcement using Nutshell's task automation or an external monitoring tool.

  • Inventory and parts data does not map to Nutshell

    ServiceMax manages bin locations, stock levels, parts reservations, and purchase orders as part of its field inventory module. Nutshell has no inventory management capability — it tracks products or services as line items in Deals but does not maintain stock quantities or bin locations. Parts consumed on Work Orders can be recorded as a text summary in the Deal's activity note, but Nutshell will not track parts availability or trigger reorder alerts. If parts management is critical to your operations, plan to keep a separate inventory system post-migration.

  • Technician-to-Nutshell user resolution requires pre-migration planning

    ServiceMax technicians (dispatch resources) may not all be Nutshell users — they may be field-only accounts that should not appear in your sales CRM. FlitStack AI resolves owners by email match, but your team must define which ServiceMax resources map to Nutshell People and which are excluded. Unmatched email addresses are flagged in the pre-migration audit so you can either invite those users to Nutshell or assign their records to a fallback owner before the migration runs.

Migration approach

Six steps for a successful ServiceMax to Nutshell data migration

  1. Audit ServiceMax data model and define the migration boundary

    We connect to your ServiceMax instance using scoped read access and inventory all standard and custom objects, Work Order history, Asset records, and Contact/Account data. We produce a migration scope document that lists every object we will import, every object we will exclude (SFM Transactions, Wizards, Technical Attributes, SPM Calculation Methods, Inventory records), and a field-level map for each included object. Your team reviews and approves the scope before we proceed.

  2. Create Nutshell custom fields for FSM data

    Before data loads, we create the custom fields on Nutshell's Deal and Company objects that will hold ServiceMax FSM data: work order status, priority, scheduled date, asset serial number, asset status, install date, and SLA reference fields. Nutshell's custom field creation is straightforward via their API and does not require a sandbox since custom fields add without overwriting existing data.

  3. Resolve owners and map Work Orders to Deals

    We run owner resolution against Nutshell user accounts using email as the matching key. Unmatched ServiceMax owners are flagged for your team to either invite to Nutshell or assign to a fallback owner. We then run the Work Order to Deal transformation: each ServiceMax Work Order becomes a Nutshell Deal with FSM custom fields populated, linked Contact resolved to a Nutshell Person, and linked Account resolved to a Nutshell Company.

  4. Run a sample migration with field-level diff

    We begin with a representative data sample—typically 100 to 300 records spanning Work Orders, Assets, Contacts, and Accounts—to validate the migration logic before committing to a full load. During this phase, we generate a detailed field-level comparison report that juxtaposes source ServiceMax values against the resulting Nutshell records. This allows you to confirm critical mappings including work order status translation, priority field population, asset-to-company linkage accuracy, contact-to-person resolution, and owner assignment logic. Any discrepancies surface immediately so corrections can be applied before the production migration proceeds.

  5. Execute full migration with delta-pickup window

    The full data set loads via Nutshell's JSON-RPC API using batched inserts to respect rate limits on both platforms. A delta-pickup window of 24–48 hours runs after the initial load to capture any ServiceMax records modified or created during the cutover period. An audit log records every operation, and one-click rollback is available if reconciliation fails or the field-level diff reveals unexpected mapping behavior.

Platform deep dives

Context on both ends of the pair

ServiceMax logo

ServiceMax

Source

Strengths

  • Deep Salesforce integration means customer and contact data stays unified without duplicate entry or sync middleware.
  • Comprehensive asset lifecycle management with entitlement enforcement, warranty tracking, and contract coverage logic built in.
  • Preventive maintenance scheduling with counter-based triggers and interval rules reduces reactive service and improves contract retention.
  • Mobile app for iOS and Android gives technicians offline access to Work Orders, Asset history, and form data in the field.
  • Technical Attributes framework models complex product configurations and links them to Assets for smarter diagnosis and parts matching.

Weaknesses

  • Configuration complexity requires specialized Salesforce/ServiceMax administrators; the learning curve is steep for new teams.
  • Cost structure compounds quickly—licensing is Salesforce-based per-user, and implementation often requires external consultants with ServiceMax-specific expertise.
  • Mobile app performance degrades in low-connectivity environments, and the browser mode lacks feature parity for pricing and billing sections.
  • Custom SFM Transactions and Wizards are brittle when Salesforce releases platform updates, causing re-testing cycles.
  • Limited native BI and reporting; cross-object analytics require additional tooling beyond Salesforce Reports.
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 ServiceMax 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

    ServiceMax: Salesforce API limits apply—reported ~5,000 API calls per org per 24-hour rolling window, with per-application limits within that.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most ServiceMax-to-Nutshell migrations complete in 48–72 hours for under 25,000 Work Order and Asset records. Larger setups with extensive work order history or multiple custom FSM fields extend to 5–10 days. The longest planning step is documenting which ServiceMax FSM configurations should be exported as a rebuild reference versus excluded entirely — that decision drives the scope document before any data moves.

Adjacent paths

Related migrations to explore

Ready when you are

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