CRM migration

Migrate from Aidoo Mobile to Nutshell

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

Aidoo Mobile logo

Aidoo Mobile

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

12 of 12

objects map 1:1 between Aidoo Mobile and Nutshell.

Complexity

BStandard

Timeline

24–48 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Aidoo Mobile is a field service management platform built around work orders, technician scheduling, asset tracking, and route optimization. Nutshell is a sales CRM built around People, Accounts, Deals, and Activities. The two platforms share a people-and-companies data layer but diverge sharply on field-service logic: Aidoo work orders have no native Nutshell equivalent, so FlitStack AI translates them to Nutshell Deals with custom fields capturing Aidoo status, priority, job type, and site address. Custom fields on Aidoo equipment records, parts inventories, and service histories map to Nutshell People/Account custom fields or Notes depending on field cardinality. Aidoo technician records land as Nutshell People with a Role custom field. Aidoo workflows, route-optimization rules, and scheduling automations do not transfer — FlitStack exports workflow definitions as a rebuild reference for Nutshell administrators. The migration runs against Nutshell's JSON-RPC API using scoped read access on Aidoo Mobile so teams keep working during cutover.

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

Aidoo Mobile logo

Aidoo Mobile

What's pushing teams away

  • Low overall review volume and 3.5/5 average rating signal a thinner support community than Jobber, Housecall Pro, or ServiceTitan.
  • Ranks 295th of 351 field service systems on ITQlick — suggesting the product has fallen behind on feature pace versus market leaders.
  • No published API documentation visible on the vendor site; custom integrations require sales engagement.
  • Pricing is quote-based — actual rates are not transparent and require contacting sales.
  • Smaller integration ecosystem than ServiceTitan or Salesforce Field Service, limiting fit for businesses with complex back-office stacks.

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

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

Aidoo Mobile

Contact / Customer

maps to

Nutshell

Person

1:1
Fully supported

Aidoo Mobile customer records (name, email, phone, address) map directly to Nutshell People. Original Aidoo create dates are preserved as a custom datetime field since Nutshell's native CreatedDate reflects migration time. Owner resolution happens via email match against Nutshell users — unmatched contacts receive a migration-owner fallback.

Aidoo Mobile

Company / Organization

maps to

Nutshell

Account

1:1
Fully supported

Aidoo Mobile company records (name, domain, industry, employee count, annual revenue) map 1:1 to Nutshell Accounts. Multi-location companies in Aidoo (parent/branch structure) map to Nutshell Account with the primary address, and branch locations surface as Notes for reference. If circular parent references exist in Aidoo, FlitStack flags them before migration.

Aidoo Mobile

Work Order

maps to

Nutshell

Deal

1:1
Fully supported

Aidoo Mobile work orders are the most significant migration object. Nutshell has no native FSM work-order entity, so FlitStack maps Aidoo work orders to Nutshell Deals and appends Aidoo FSM fields (status, priority, job type, site address, expected start/completion dates, assigned technician) as Nutshell custom fields. The Deal Name defaults to Aidoo work order ID plus site address. Stage is set based on Aidoo status value mapping.

Aidoo Mobile

Custom Field (Contact-level)

maps to

Nutshell

Person custom field

1:1
Fully supported

Aidoo Mobile custom fields on customer records map to Nutshell People custom fields. Plan-tier limits apply: Foundation has fewer custom fields than Pro/Enterprise. FlitStack audits the Aidoo custom field inventory against the target Nutshell plan before migration and flags any fields that exceed plan limits, prioritizing the most-used fields for migration and documenting the rest for manual post-migration creation.

Aidoo Mobile

Custom Field (Company-level)

maps to

Nutshell

Account custom field

1:1
Fully supported

Aidoo Mobile equipment and asset custom fields associated with companies map to Nutshell Account custom fields. Field data types (text, number, date, picklist) are preserved during mapping. Picklist values from Aidoo are replicated as Nutshell choice options on the corresponding custom field. If Aidoo stores multi-select picklists, these map to Nutshell multi-choice custom fields where supported by plan tier.

Aidoo Mobile

Activity (call, email, meeting, note)

maps to

Nutshell

Activity / Note

1:1
Fully supported

Aidoo Mobile activity records (service visit notes, technician emails, meeting logs) map to Nutshell Activities attached to the corresponding Person or Account record. Original activity timestamps, subject lines, and body content are preserved. FlitStack maps Aidoo activity type to Nutshell activity category (call, email, meeting, note) using the destination API's activity model. Activities without a resolvable parent record are attached to the associated Account.

Aidoo Mobile

Technician / Field Worker

maps to

Nutshell

Person

1:1
Fully supported

Aidoo Mobile technician records map to Nutshell People with a Role custom field set to 'Technician' to distinguish them from customer contacts. Technician email is used for owner resolution — if a matching Nutshell user exists by email, the Person record is assigned that user as OwnerId. Unresolved technicians are flagged for manual Nutshell user creation before the migration runs.

Aidoo Mobile

Asset / Equipment

maps to

Nutshell

Account custom field or Note

1:1
Fully supported

Aidoo Mobile asset records (equipment serial numbers, maintenance schedules, installed location) have no direct Nutshell equivalent. FlitStack maps the primary asset key fields to Account custom fields (serial_number__c, last_service_date__c, equipment_type__c) and attaches the full asset record as a Note on the linked Account. Asset-to-account linkage is resolved via Aidoo's customer-association field before migration.

Aidoo Mobile

Parts / Materials (line items on work order)

maps to

Nutshell

Deal Product or custom field

1:1
Fully supported

Aidoo Mobile parts used per work order map to Nutshell Deal Products if the parts list is simple (SKU, quantity, unit cost). For complex Aidoo parts structures with lot numbers, expiry dates, or bin locations, FlitStack creates Deal custom fields to preserve the data rather than forcing it into the Products object. This avoids forcing Aidoo FSM part logic into a sales-focused Products model.

Aidoo Mobile

User / Owner

maps to

Nutshell

Nutshell User

1:1
Fully supported

Aidoo Mobile owner IDs are resolved against Nutshell users by email address. Unmatched owners (technicians not yet created as Nutshell users, or inactive Aidoo users) are flagged before migration with a resolution recommendation — invite the user to Nutshell or assign records to a migration fallback owner. No record lands without a resolved Nutshell owner.

Aidoo Mobile

Work Order Pipeline / Status

maps to

Nutshell

Deal Stage

1:1
Fully supported

Aidoo Mobile work order statuses (New, Scheduled, In Progress, On Hold, Completed, Cancelled) map to Nutshell Deal stage values. The mapping plan is delivered before migration runs so Nutshell stages can be pre-created to match Aidoo status names exactly. Probability and forecast category are assigned per stage based on Aidoo status-to-probability data.

Aidoo Mobile

Attachment / File

maps to

Nutshell

Note attachment or URL field

1:1
Fully supported

Aidoo Mobile file attachments on work orders or customer records are downloaded and re-uploaded to Nutshell's storage. Inline images in Aidoo notes are extracted, re-hosted, and the image URL is embedded in the Nutshell Note body. Nutshell's file size limits apply — files exceeding the limit are flagged and documented for manual re-upload post-migration.

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.

Aidoo Mobile logo

Aidoo Mobile gotchas

High

Aidoo Mobile has no publicly documented API

Medium

Pricing is not publicly published

Low

Limited review corpus for data quality signals

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 API rate limits on find operations throttle large Aidoo data exports

    Nutshell's JSON-RPC API rate-limits find requests (findLeads, findContacts, findAccounts) with non-stub responses, and also applies throttling to excessive get requests. Aidoo Mobile exports with 50,000+ work order records will hit these limits during the migration pull phase. FlitStack batches exports using cursor-based pagination and introduces sleep intervals to stay within Nutshell's rate floor. The migration plan documents the expected export duration for large datasets so teams can plan the cutover window accordingly. Teams should ensure the Nutshell account used for migration does not have impersonation disabled, since impersonation-enabled keys allow actions to be logged against the appropriate Nutshell user.

  • Work order FSM logic has no native Nutshell equivalent — architectural choice required before migration

    Aidoo Mobile work orders carry FSM-specific fields (job type, site address, assigned technician, parts used, service schedule) that do not map to any native Nutshell object. FlitStack resolves this by translating work orders to Nutshell Deals and appending Aidoo FSM fields as custom fields on the Deal. However, this means work orders appear as Deals in Nutshell's pipeline view — which may not reflect the field service workflow Aidoo Mobile users expect. Teams must decide before migration whether to show all work orders as open Deals (with FSM custom fields) or to close completed work orders and keep only open ones as Deals while archiving the rest as historical notes and activities. FlitStack surfaces this decision in the pre-migration plan and defaults to a Deal-per-open-work-order approach unless instructed otherwise.

  • Nutshell custom field limits are plan-tiered — Aidoo FSM custom field counts may exceed Foundation or Pro limits

    Nutshell restricts custom field counts by plan tier. Foundation and Pro plans have lower custom field caps than Enterprise. Aidoo Mobile setups with 15+ custom fields on work orders, 10+ custom fields on assets, and 8+ custom fields on contacts will exceed Nutshell Pro custom field limits. FlitStack audits the Aidoo custom field inventory against the target Nutshell plan before migration and delivers a prioritized list: the highest-value Aidoo custom fields migrate first; the rest are documented with field names, data types, and picklist values for post-migration manual creation in Nutshell's field management UI. This ensures no surprise field-creation failures during the migration run.

  • Aidoo Mobile workflows, route-optimization rules, and scheduling automations do not transfer to Nutshell

    Aidoo Mobile ships with field service workflows for technician scheduling, route optimization logic, and automated dispatch rules. Nutshell has no equivalent to FSM scheduling or route logic — its automation features (email sequences, stage-change triggers, activity reminders in Pro+) apply to sales processes, not field service. FlitStack does not migrate these automations. As part of the migration package, FlitStack exports Aidoo Mobile workflow definitions as a structured reference document that Nutshell administrators can use to rebuild equivalent logic using Nutshell's sales automation tools or a connected scheduling add-on. This is the most significant post-migration rebuild item and should be planned alongside the data migration.

  • Aidoo technician records must resolve to Nutshell users — uninvited technicians block migration for their assigned work orders

    Aidoo Mobile assigns work orders to technicians by internal ID. Nutshell requires an OwnerId referencing a registered Nutshell user. FlitStack resolves Aidoo technician records to Nutshell users by email match. Any technician whose email does not correspond to a Nutshell user is flagged as unresolved before the migration runs. Unresolved technicians block work order migration (since the Deal would have no OwnerId). Teams must either invite the technician to Nutshell first, or assign their work orders to a fallback owner during migration planning. FlitStack delivers a technician-resolution report as part of the pre-migration audit so this can be addressed before the migration window opens.

Migration approach

Six steps for a successful Aidoo Mobile to Nutshell data migration

  1. Audit Aidoo Mobile data model and build the migration mapping plan

    FlitStack extracts the Aidoo Mobile data model — objects, fields, custom field definitions, picklist values, and relationship links — via API. We cross-reference the Aidoo field inventory against the target Nutshell plan's custom field limits. The mapping plan defines object-level translations (Contact → Person, Work Order → Deal with custom fields, Asset → Account custom fields), value mappings for Aidoo status-to-Nutshell-stage, and a technician-resolution report listing which Aidoo technicians map to existing Nutshell users by email and which are unresolved. The plan is delivered for review before any data moves.

  2. Create Nutshell custom fields before data lands

    Before migration records are written, FlitStack creates the Nutshell custom fields required by the mapping plan — FSM fields on Deal (Job_Type__c, Site_Address__c, Priority__c, Expected_Start__c, Expected_Completion__c), custom fields on Person and Account for Aidoo custom property data, and source-system ID fields for traceability. If the target Nutshell plan's custom field limit is lower than the Aidoo field count, FlitStack prioritizes the highest-value fields and documents the rest for post-migration manual creation. Custom field creation is validated by querying the Nutshell API before the migration run proceeds.

  3. Resolve owners and run a sample migration with field-level diff

    FlitStack resolves all Aidoo owner and technician IDs to Nutshell users by email match. Unresolved owners receive a fallback assignment or are flagged for team action before the migration window. A representative sample — typically 100–500 records spanning People, Accounts, Deals (work orders), and Activities — is migrated first. FlitStack generates a field-level diff comparing source values against destination values for every mapped field so you can verify FSM field preservation (job type, site address, priority), stage mapping, and owner resolution before the full run commits.

  4. Execute full migration with delta-pickup and audit log

    The full migration runs in dependency order: Accounts first (required for Person lookups), then People, then Deals (work orders) with FSM custom fields and technician-to-owner resolution, then Activities attached to the resolved parent records. Nutshell API rate limits are respected via batch sizing and cursor pagination. A delta-pickup window (24–48 hours) captures any Aidoo records created or modified during the cutover period. Every operation is logged to an audit trail. If reconciliation counts do not match, FlitStack identifies the discrepancy record and re-runs only the affected object batch before cutover completes.

  5. Reconciliation check and cutover sign-off

    FlitStack delivers a final reconciliation report comparing Aidoo record counts by object type against Nutshell record counts. Any records that failed migration are listed with error codes. The technician-resolution status is re-verified against the final Nutshell user list. Once reconciliation passes, teams cut over to Nutshell as the system of record. Aidoo Mobile enters a read-only state during the delta window and can be decommissioned after the cutover is confirmed. FlitStack provides a rollback procedure using the pre-migration backup state if reconciliation fails and the team chooses to abort.

Platform deep dives

Context on both ends of the pair

Aidoo Mobile logo

Aidoo Mobile

Source

Strengths

  • Mobile-first technician experience with voice calling and clean UI.
  • Lower price point than enterprise FSM platforms.
  • Three-tier plan structure provides a defined upgrade path.
  • Core FSM features (dispatch, GPS, work orders, e-signature, inventory) are covered.
  • Implementation timelines (2–6 weeks per ITQlick) are shorter than enterprise FSM rollouts.

Weaknesses

  • Thin review base (3.5/5 average) compared to mainstream FSM platforms.
  • Ranked 295 of 351 FSM products by ITQlick — suggests feature pace lag.
  • No publicly documented API or integration directory.
  • Quote-only pricing for all tiers, no transparent rate card.
  • Limited integration ecosystem versus ServiceTitan, Salesforce Field Service, or Jobber.
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 manual workaround.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Aidoo Mobile and Nutshell.

  • Object compatibility

    B

    1 of 8 objects need a manual workaround.

  • 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

    Aidoo Mobile: Not publicly documented — typical SaaS limits assumed and confirmed during scoping.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most Aidoo Mobile to Nutshell migrations complete in 48–72 hours of clock time for datasets under 25,000 records. Large setups with 100,000+ work order records, or those with 30+ custom fields requiring Nutshell custom field creation across multiple entities, extend to 5–7 days. Nutshell's API rate limits on find operations are the primary variable that affects large-export pacing. Mapping Aidoo work orders to Nutshell Deals is the longest planning step — confirming which Aidoo FSM fields become Deal custom fields and which become Notes.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Aidoo Mobile.
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