CRM migration
Field-level mapping, validation, and rollback between Aidoo Mobile and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Aidoo Mobile
Source
Nutshell
Destination
Compatibility
12 of 12
objects map 1:1 between Aidoo Mobile and Nutshell.
Complexity
BStandard
Timeline
24–48 hours
Overview
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.
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 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
Nutshell
Person
1:1Aidoo 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
Nutshell
Account
1:1Aidoo 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
Nutshell
Deal
1:1Aidoo 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)
Nutshell
Person custom field
1:1Aidoo 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)
Nutshell
Account custom field
1:1Aidoo 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)
Nutshell
Activity / Note
1:1Aidoo 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
Nutshell
Person
1:1Aidoo 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
Nutshell
Account custom field or Note
1:1Aidoo 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)
Nutshell
Deal Product or custom field
1:1Aidoo 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
Nutshell
Nutshell User
1:1Aidoo 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
Nutshell
Deal Stage
1:1Aidoo 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
Nutshell
Note attachment or URL field
1:1Aidoo 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.
| Aidoo Mobile | Nutshell | Compatibility | |
|---|---|---|---|
| Contact / Customer | Person1:1 | Fully supported | |
| Company / Organization | Account1:1 | Fully supported | |
| Work Order | Deal1:1 | Fully supported | |
| Custom Field (Contact-level) | Person custom field1:1 | Fully supported | |
| Custom Field (Company-level) | Account custom field1:1 | Fully supported | |
| Activity (call, email, meeting, note) | Activity / Note1:1 | Fully supported | |
| Technician / Field Worker | Person1:1 | Fully supported | |
| Asset / Equipment | Account custom field or Note1:1 | Fully supported | |
| Parts / Materials (line items on work order) | Deal Product or custom field1:1 | Fully supported | |
| User / Owner | Nutshell User1:1 | Fully supported | |
| Work Order Pipeline / Status | Deal Stage1:1 | Fully supported | |
| Attachment / File | Note attachment or URL field1: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.
Aidoo Mobile gotchas
Aidoo Mobile has no publicly documented API
Pricing is not publicly published
Limited review corpus for data quality signals
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 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.
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.
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.
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.
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
Aidoo Mobile
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a manual workaround.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Aidoo Mobile and Nutshell.
Object compatibility
1 of 8 objects need a manual workaround.
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
Aidoo Mobile: Not publicly documented — typical SaaS limits assumed and confirmed during scoping.
Data volume sensitivity
Aidoo Mobile 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 Aidoo Mobile to Nutshell migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Aidoo Mobile
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.