CRM migration
Field-level mapping, validation, and rollback between ServiceMax and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
ServiceMax
Source
Nutshell
Destination
Compatibility
12 of 12
objects map 1:1 between ServiceMax and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
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.
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 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)
Nutshell
Deal
1:1ServiceMax 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
Nutshell
Deal Line Item / Activity Note
1:1Work 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)
Nutshell
Company
1:1ServiceMax 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)
Nutshell
Person
1:1ServiceMax 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
Nutshell
Company
1:1ServiceMax 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
Nutshell
Company custom fields
1:1Service 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
Nutshell
Company custom fields
1:1Entitlements 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
Nutshell
Activity (Task)
1:1Preventive 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
Nutshell
Person
1:1ServiceMax 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)
Nutshell
Activity
1:1ServiceMax 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
Nutshell
File attachment on Person or Deal
1:1Files 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
Nutshell
Not migratable
1:1ServiceMax 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.
| ServiceMax | Nutshell | Compatibility | |
|---|---|---|---|
| Work Order (SVMXC__Service_Order__c) | Deal1:1 | Fully supported | |
| Work Order Line Item | Deal Line Item / Activity Note1:1 | Fully supported | |
| Asset (SVMXC__Asset__c) | Company1:1 | Fully supported | |
| Contact (Contact) | Person1:1 | Fully supported | |
| Account | Company1:1 | Fully supported | |
| Service Contract | Company custom fields1:1 | Fully supported | |
| Entitlement | Company custom fields1:1 | Fully supported | |
| Preventive Maintenance Process | Activity (Task)1:1 | Fully supported | |
| Technician / Resource | Person1:1 | Fully supported | |
| Activity History (Calls, Emails, Logs) | Activity1:1 | Fully supported | |
| Attachment / File | File attachment on Person or Deal1:1 | Fully supported | |
| SFM Transaction / SFM Wizard / Mobile Config | Not migratable1: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.
ServiceMax gotchas
API call limits reset on a 24-hour rolling window
SFM Transaction and Wizard dependencies create migration loops
Configuration Profile migration excludes Default profiles
Large Technical Attributes configurations slow the Migration Tool UI
Pricing and Billing UI missing from browser mode
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 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.
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.
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.
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.
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
ServiceMax
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 ServiceMax 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
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
ServiceMax 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 ServiceMax to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your ServiceMax 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 ServiceMax
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.