CRM migration
Field-level mapping, validation, and rollback between STEL Order and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
STEL Order
Source
Nutshell
Destination
Compatibility
12 of 12
objects map 1:1 between STEL Order and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
STEL Order is a field-service management platform that combines CRM, job scheduling, work orders, inventory, and invoicing in a single application. Nutshell is a purpose-built CRM for small-to-mid-market sales teams that handles contacts, accounts, deals, activities, and built-in email marketing without field-service or inventory modules. The migration carries STEL Order's client records, product catalog, quotes, and activity history into Nutshell's data model using STEL Order's REST API and Nutshell's JSON-RPC API. Objects with direct equivalents — clients as People, companies as Companies, products as Products, quotes as Deals — migrate cleanly. Work orders have no native Nutshell equivalent; we reconstruct them as Deals with custom fields (Work_Order_ID__c, Work_Order_Status__c, Work_Order_Type__c) plus a linked Note for job details. Invoice records store as Deals with custom invoice fields. Integration credentials for Stripe and PayPal cannot transfer; those connections must be rebuilt in Nutshell's ecosystem. We run a sample migration against a representative record slice, validate field-level mappings, then execute the full cutover with a 24–48 hour delta pickup window for any in-flight changes during the switch.
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 STEL Order 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.
STEL Order
Client (Contact)
Nutshell
Person
1:1STEL Order clients map directly to Nutshell People. The client's name, email, phone, address, and company association all have direct Nutshell Person fields. Owner resolution uses email matching against Nutshell users. Clients without a company association land as standalone People records.
STEL Order
Company
Nutshell
Company
1:1STEL Order companies map to Nutshell Companies with a direct 1:1 field correspondence for name, domain, industry, employee count, and annual revenue. The industry pick-list in STEL Order may need value mapping where terminology differs from Nutshell's industry taxonomy. Additionally, any custom industry classifications defined in STEL Order are reviewed and aligned to available Nutshell options during the migration planning phase.
STEL Order
Product / Service
Nutshell
Product
1:1STEL Order product catalog items (name, description, unit price, SKU) migrate to Nutshell Products. Inventory quantities stored in STEL Order cannot map to a Nutshell field since Nutshell does not include inventory tracking; we store the last-known quantity as a custom field on the Product record for reference.
STEL Order
Quote
Nutshell
Deal
1:1STEL Order quotes map to Nutshell Deals with quote name as Deal name, monetary amount as Deal value, and the quote status (Sent, Accepted, Declined) mapped to corresponding Nutshell pipeline stages. Product line items on STEL Order quotes become Deal line items in Nutshell.
STEL Order
Invoice
Nutshell
Deal (with custom fields)
1:1Nutshell has no native invoice object. We map STEL Order invoices to Deals with custom fields capturing Invoice_Number__c, Invoice_Date__c, Invoice_Amount__c, and Invoice_Status__c. The original invoice PDF, if stored in STEL Order, is attached to the Deal as a Nutshell file reference.
STEL Order
Work Order / Job
Nutshell
Deal (with custom fields) + Note
1:1STEL Order work orders have no direct Nutshell equivalent. We map them to Deals with custom fields: Work_Order_ID__c (original STEL Order ID for traceability), Work_Order_Type__c (scheduling, maintenance, repair), Work_Order_Status__c (open, in-progress, completed), and Scheduled_Date__c. The work order description and technician notes become a linked Nutshell Note attached to the Deal.
STEL Order
Client Address
Nutshell
Person address fields
1:1STEL Order stores client address as structured fields (street, city, state, postal code, country). These map to the corresponding address fields on the Nutshell Person record. For clients with multiple addresses, the primary address maps to Person fields and additional addresses are stored in a custom field as a formatted text reference.
STEL Order
Activity: Call
Nutshell
Task (Type: Call)
1:1STEL Order call logs (subject, call date, duration, outcome notes) migrate as Nutshell Tasks with Task Type set to 'Call'. Original timestamps and the assigned technician (owner) are preserved. The parent record link to the STEL Order client or work order maps to the corresponding Nutshell Person or Deal.
STEL Order
Activity: Note / Work Note
Nutshell
Note
1:1STEL Order work notes and general notes migrate as Nutshell Notes attached to the relevant Person, Company, or Deal record. Original creation timestamps and note authors are preserved. Rich-text formatting in STEL Order notes is converted to plain text for Nutshell's Note model.
STEL Order
Activity: Email
Nutshell
Task (Type: Email)
1:1STEL Order email activity (subject, body, sent/received date, direction) migrates as Nutshell Tasks with Type 'Email'. The parent Person or Deal association is preserved. Email body content migrates as the Task description. Attachments referenced in STEL Order emails are noted in the Task record, though actual file migration depends on whether the files are accessible via the STEL Order API.
STEL Order
User / Staff Member
Nutshell
Nutshell User
1:1STEL Order staff records (name, email, role) map to Nutshell Users via email matching. Unmatched staff members are flagged before migration. Nutshell user roles (admin, standard) are assigned based on the staff member's role in STEL Order. If a staff member's role does not have a direct equivalent in Nutshell, the account is assigned the standard user role pending review.
STEL Order
Custom Field (Client)
Nutshell
Custom Field on Person
1:1STEL Order custom fields attached to clients migrate as Nutshell custom fields on the Person object. Field data type is preserved (text, number, date, pick-list). For pick-list custom fields, the pick-list values are created in Nutshell and mapped value-by-value. Required field settings in STEL Order are reviewed, though Nutshell's field requirements may differ from STEL Order's validation rules.
| STEL Order | Nutshell | Compatibility | |
|---|---|---|---|
| Client (Contact) | Person1:1 | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Product / Service | Product1:1 | Fully supported | |
| Quote | Deal1:1 | Fully supported | |
| Invoice | Deal (with custom fields)1:1 | Fully supported | |
| Work Order / Job | Deal (with custom fields) + Note1:1 | Fully supported | |
| Client Address | Person address fields1:1 | Fully supported | |
| Activity: Call | Task (Type: Call)1:1 | Fully supported | |
| Activity: Note / Work Note | Note1:1 | Fully supported | |
| Activity: Email | Task (Type: Email)1:1 | Fully supported | |
| User / Staff Member | Nutshell User1:1 | Fully supported | |
| Custom Field (Client) | Custom Field on Person1: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.
STEL Order gotchas
Offline-created records may not sync to cloud before export
Bulk import requires manual CSV/Excel formatting
Payment gateway references do not transfer as linked transactions
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
Connect to STEL Order and audit the data landscape
FlitStack AI establishes a scoped read-only API connection to your STEL Order account. We pull a full export of all clients, companies, products, quotes, work orders, invoices, activities, and custom field definitions. We cross-reference each object against Nutshell's API schema to identify which fields have direct equivalents, which require custom field creation, and which STEL Order objects (work orders, invoices) have no native Nutshell counterpart. The audit output becomes the field-mapping specification reviewed with your team before any data movement begins.
Create custom fields in Nutshell for work orders and invoices
Before data migration begins, we create the required custom fields in Nutshell: Work_Order_ID__c, Work_Order_Type__c, Work_Order_Status__c, Scheduled_Date__c on the Deal object; Invoice_Number__c, Invoice_Date__c, Invoice_Amount__c, Invoice_Status__c on the Deal object; Stock_Quantity__c on the Product object; and STEL_Order_ID__c on the Person object for traceability. Custom pick-list values for work-order types, statuses, and invoice statuses are created in Nutshell and mapped value-by-value to STEL Order's original values. This step requires a Nutshell admin account with field-creation permissions.
Resolve STEL Order users and staff to Nutshell users
STEL Order staff members and quote/work-order owners are matched to existing Nutshell users by email address. Unmatched staff records are flagged in the pre-migration report — your team decides whether to create new Nutshell user accounts before migration or assign those records to a fallback Nutshell user. No record migrates without a resolved owner; unresolved owners would create orphaned Deals or Tasks in Nutshell with no assigned user.
Run a sample migration and validate field-level mappings
A representative sample of 100–500 records — spanning clients, companies, products, quotes, work orders, and activity history — migrates first into a Nutshell staging environment (or the live account with your approval). We generate a field-level diff showing every mapped field, its source value in STEL Order, and its destination value in Nutshell. Your team reviews the output and flags any fields that need remapping, any work-order custom field labels that should be renamed, or any Deal pipeline stages that need adjustment before the full migration commits.
Execute full migration with delta-pickup window
The full migration runs against your live Nutshell account. Companies, People, Products, Deals (quotes), custom-field Deal records (work orders and invoices), and activity history load in sequence so foreign-key relationships resolve correctly — Companies before People, Products before Deals. A delta-pickup window of 24–48 hours captures any new STEL Order records or edits made during the cutover. An audit log records every operation. If reconciliation reveals discrepancies, one-click rollback reverts the Nutshell state to the pre-migration snapshot.
Platform deep dives
STEL Order
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 STEL Order 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
STEL Order: Not publicly documented.
Data volume sensitivity
STEL Order 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 STEL Order to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your STEL Order 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 STEL Order
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.