CRM migration

Migrate from STEL Order to Nutshell

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

STEL Order logo

STEL Order

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

12 of 12

objects map 1:1 between STEL Order and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

STEL Order logo

STEL Order

What's pushing teams away

  • Limited international documentation and primarily Spanish-language support creates friction for non-Spanish speaking teams evaluating the platform for global use.
  • API documentation is not publicly detailed, making custom integrations and automated data pipelines difficult to implement without direct vendor support.
  • Small review sample size (4 verified reviews) makes it difficult to assess long-term reliability and identify systemic issues before committing to the platform.

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

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)

maps to

Nutshell

Person

1:1
Fully supported

STEL 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

maps to

Nutshell

Company

1:1
Fully supported

STEL 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

maps to

Nutshell

Product

1:1
Fully supported

STEL 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

maps to

Nutshell

Deal

1:1
Fully supported

STEL 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

maps to

Nutshell

Deal (with custom fields)

1:1
Fully supported

Nutshell 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

maps to

Nutshell

Deal (with custom fields) + Note

1:1
Fully supported

STEL 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

maps to

Nutshell

Person address fields

1:1
Fully supported

STEL 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

maps to

Nutshell

Task (Type: Call)

1:1
Fully supported

STEL 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

maps to

Nutshell

Note

1:1
Fully supported

STEL 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

maps to

Nutshell

Task (Type: Email)

1:1
Fully supported

STEL 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

maps to

Nutshell

Nutshell User

1:1
Fully supported

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

maps to

Nutshell

Custom Field on Person

1:1
Fully supported

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

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.

STEL Order logo

STEL Order gotchas

High

Offline-created records may not sync to cloud before export

Medium

Bulk import requires manual CSV/Excel formatting

Medium

Payment gateway references do not transfer as linked transactions

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

  • Work orders have no native Nutshell equivalent and require custom-field reconstruction

    STEL Order's work orders are central to the platform — they track job type, status, scheduled date, assigned technician, and job details. Nutshell has no Work Order or Job object; it only supports People, Companies, Leads, Deals, Tasks, and Events. We map STEL Order work orders to Deals with custom fields (Work_Order_ID__c, Work_Order_Type__c, Work_Order_Status__c, Scheduled_Date__c) and attach the job description as a Nutshell Note. This preserves the full work-order history but requires your team to review the custom field labels in Nutshell after migration. The more granular the work-order tracking in STEL Order, the more custom fields we create on the Deal object, which increases migration scoping.

  • Invoice data must be stored as custom fields on Deal records

    Nutshell does not include a native invoice object — there is no Invoice, Billing, or Accounts Receivable module in the platform. STEL Order invoice records (invoice number, date, amount, status, line items) cannot map to a native Nutshell object. We store invoice data as custom fields on the corresponding Deal record (Invoice_Number__c, Invoice_Date__c, Invoice_Amount__c, Invoice_Status__c). If your team relies on invoice history for accounts-receivable follow-up, this representation is visible in Nutshell but requires your team to adapt their workflow to Deal-based invoice references rather than a dedicated invoice register.

  • Inventory quantities cannot be tracked in Nutshell

    STEL Order includes multi-location inventory management — tracking stock levels per product across warehouses and service vehicles. Nutshell does not include an inventory management module. STEL Order product stock quantities map to a custom field on the Nutshell Product record (Stock_Quantity__c) as a static reference value, but Nutshell does not decrement or update this quantity automatically when deals close or products are consumed. If inventory tracking is critical to your operations, you will need a separate inventory management tool or a custom integration to maintain live stock data after migration.

  • Stripe and PayPal payment integrations do not transfer

    STEL Order's native payment integrations with Stripe and PayPal are account-level credentials configured within the STEL Order platform — they are not data that can be exported and re-imported into Nutshell. After migration, your team must configure new Stripe or PayPal connections within Nutshell (or via a third-party integration such as Zapier) to enable online payment collection on Nutshell-stored invoices and deals. Any existing payment links, webhook configurations, or accounting reconciliation rules built around STEL Order's payment processing need to be rebuilt.

  • Offline mobile work-order workflows do not exist in Nutshell

    STEL Order's iOS and Android mobile apps support offline access to job details, work notes, invoice generation, and GPS tracking without internet connectivity — a critical feature for field technicians working in basements, rural sites, or inside buildings with poor signal. Nutshell's mobile app handles contact lookup, task management, and pipeline updates but does not include offline work-order creation, job-note documentation, or GPS field tracking. Teams that rely on offline mobile workflows in STEL Order should evaluate whether Nutshell's mobile capabilities meet their field-service needs before committing to the migration, as those workflows will require a different approach post-migration.

Migration approach

Six steps for a successful STEL Order to Nutshell data migration

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

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

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

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

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

Context on both ends of the pair

STEL Order logo

STEL Order

Source

Strengths

  • Comprehensive FSM suite combining scheduling, invoicing, inventory, and CRM in a single platform
  • Offline-capable mobile apps for Android and iOS enable field technicians to work without internet
  • Bulk CSV and Excel import for rapid data onboarding from spreadsheets or legacy systems
  • Stripe and PayPal payment integration provides immediate online payment collection
  • Per-user pricing with 1-on-1 onboarding and 24/7 support offers accessible entry for small businesses

Weaknesses

  • Limited publicly available API documentation restricts custom integration development
  • Primarily Spanish-language documentation and support may hinder non-Spanish speaking users
  • Small verified review sample (4 reviews) makes platform reliability assessment difficult
  • File-based bulk import (CSV/Excel) lacks real-time sync capabilities for ongoing data movement
  • Equipment and asset management features are functional but less mature than dedicated CMMS platforms
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 STEL Order 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

    STEL Order: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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 consultation

Most STEL Order to Nutshell migrations complete in 48–72 hours of clock time for databases under 25,000 records. Larger setups with extensive work-order history, large product catalogs, or multiple custom fields extend to 5–7 days. The longest planning step is mapping STEL Order work-order and invoice fields to Nutshell custom fields — that field-creation work must be completed before data loads begin. A sample migration run adds 4–8 hours but prevents full-run surprises.

Adjacent paths

Related migrations to explore

Ready when you are

Move from STEL Order.
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