CRM migration
Field-level mapping, validation, and rollback between FotoNotes and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
FotoNotes
Source
Nutshell
Destination
Compatibility
9 of 10
objects map 1:1 between FotoNotes and Nutshell.
Complexity
BStandard
Timeline
24–72 hours
Overview
FotoNotes is a field-service platform built around inspection workflows, photo documentation, and property-containers with nested work orders. Nutshell is a SMB-focused CRM organized around accounts, people, leads, and deals. The two data models diverge significantly: FotoNotes uses a hierarchical container/containee structure for properties and inspections, while Nutshell uses flat account and contact records with a separate deal object for opportunities. FlitStack AI extracts FotoNotes projects and their nested containees, maps customer and vendor contact records into Nutshell people, and translates work order status into Nutshell deal stages or custom fields depending on your workflow. Photo attachments from inspections are preserved as file attachments on the corresponding Nutshell account or person record. The migration runs against Nutshell's REST API with batch upsert. Workflow templates, custom work order forms, and role-based routing logic in FotoNotes have no direct Nutshell equivalent — these must be rebuilt manually using Nutshell's automation tools or documented from FotoNotes exports for rebuild reference.
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 FotoNotes 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.
FotoNotes
Property (Container)
Nutshell
Account
1:1FotoNotes property records map to Nutshell accounts. The property name becomes the account name, and address fields (street, city, state, ZIP) map directly to Nutshell's address fields. We preserve the property ID as Source_System_ID__c for delta-run deduplication. Multi-property portfolios each become individual account records.
FotoNotes
Containee / Work Order
Nutshell
Deal
1:1Each FotoNotes work order (containee) maps to a Nutshell deal linked to the parent property account. Work order status (New, In Progress, On Hold, Completed) maps to Nutshell deal stage values via value mapping. If Nutshell's standard stages do not match your workflow, we create custom stage values before migration and map FotoNotes status values one-by-one.
FotoNotes
Work Order Template
Nutshell
Custom Field Group
1:1FotoNotes custom fields defined on work order templates have no native equivalent in Nutshell deal records. We create custom fields on Nutshell deals for each template-defined field — text, number, date, and pick-list types translate directly; formula and computed fields are preserved as read-only custom fields with their last-calculated value.
FotoNotes
Customer / Owner Contact
Nutshell
Person
1:1FotoNotes customer records (property owners or clients) map to Nutshell person records linked to the account representing their property. We map name, email, phone, and address fields directly. The FotNotes contact's role as 'Customer' is stored as a custom field on the Nutshell person record since Nutshell does not have a native customer role designation.
FotoNotes
Field User / Vendor Contact
Nutshell
Person
many:1FotoNotes field users and vendor contacts are merged into Nutshell person records under the same account. We do not create separate account records per vendor — multiple vendor contacts land as separate person records under the relevant property account. Their role (Field User, Vendor Admin, Vendor Field User) is preserved as a custom pick-list field on the person record.
FotoNotes
Inspection Photo
Nutshell
File Attachment
1:1FotoNotes inspection photos attach to the corresponding work order deal record in Nutshell. Photo metadata (caption, annotation text, timestamp) is stored as a text note on the file attachment. Bulk photo exports require URL-based re-upload to Nutshell's file storage since Nutshell does not host photos natively — we use the Nutshell API file upload endpoint.
FotoNotes
Batch PDF Report
Nutshell
Note
1:1FotoNotes batch PDF reports generated from multiple inspections have no Nutshell equivalent. We store a link to the source PDF (if accessible via FotoNotes API) as a URL custom field on the deal record, or preserve the report content as a long-text Note if the PDF content is extractable. Native PDF hosting in Nutshell is not supported.
FotoNotes
Activity Log Entry
Nutshell
Activity
1:1FotoNotes activity log entries (status changes, assignment updates, comments) map to Nutshell activities linked to the corresponding deal. Activity timestamps and the acting user name are preserved. The activity type is stored as a custom field since Nutshell's activity model is less granular than FotoNotes' event log.
FotoNotes
User / Owner Assignment
Nutshell
User / Person Owner
1:1FotoNotes user assignments on work orders are resolved by email match against Nutshell users. If a FotoNotes user has no matching Nutshell account, we create a Nutshell person record and flag the unassigned owner in the migration report for your team to resolve before or after migration.
FotoNotes
Portal Admin / Manager Role
Nutshell
Custom Field on Person
1:1FotoNotes role assignments (Portal Admin, Manager) do not map to Nutshell's user management model since Nutshell does not have equivalent portal admin roles. We preserve the role designation as a custom pick-list field on the relevant person record for audit and reference purposes.
| FotoNotes | Nutshell | Compatibility | |
|---|---|---|---|
| Property (Container) | Account1:1 | Fully supported | |
| Containee / Work Order | Deal1:1 | Fully supported | |
| Work Order Template | Custom Field Group1:1 | Fully supported | |
| Customer / Owner Contact | Person1:1 | Fully supported | |
| Field User / Vendor Contact | Personmany:1 | Fully supported | |
| Inspection Photo | File Attachment1:1 | Fully supported | |
| Batch PDF Report | Note1:1 | Fully supported | |
| Activity Log Entry | Activity1:1 | Fully supported | |
| User / Owner Assignment | User / Person Owner1:1 | Fully supported | |
| Portal Admin / Manager Role | 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.
FotoNotes gotchas
Container-to-contained field inheritance is implicit
Batch PDF reports are the only bulk export mechanism
Vendor sub-accounts require hierarchical mapping
FotoNotes is now SiteCapture — documentation split
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
Profile FotoNotes data and build the migration map
FlitStack AI connects to your FotoNotes account via API and extracts all property containers, work order records, contact lists, photo metadata, and activity log entries. We profile record counts, custom field types per template, and container nesting depth. The output is a migration map specifying every object mapping, field-level translation rule, and photo re-upload plan. You review and approve the map before any data moves.
Create Nutshell custom fields and prepare the schema
Before migration, you create the custom fields identified in the migration map on Nutshell deals and person records. FlitStack AI delivers a step-by-step field creation checklist with field names, types, and pick-list values. We recommend completing this step 2–3 business days before the migration run so any questions about field configuration can be resolved without delaying the cutover and ensure consistent data mapping across all teams.
Run a sample migration and generate a field-level diff
A representative slice of 50–200 FotoNotes records migrates first — spanning a mix of property accounts, work order deals, contacts, and photos. We generate a field-level diff showing every source value and its destination value side-by-side. You verify thoroughly status-to-stage mapping, photo attachment linking, owner resolution, and custom field population. Any mapping adjustments are applied before the full run commits.
Execute the full migration with delta-pickup
The full migration runs against Nutshell's JSON-RPC API in batch upsert mode. FotoNotes remains fully operational during the migration — your team continues using FotoNotes normally. A delta-pickup window (24–48 hours) after the initial load captures any new work orders or status changes made during the cutover window. All operations are logged in an audit trail; one-click rollback is available if reconciliation fails.
Deliver audit log, reconciliation report, and post-migration support
FlitStack AI delivers a full audit log listing every record migrated, the transformation applied, and the timestamp. A reconciliation report compares FotoNotes record counts and field totals against Nutshell destination counts. We provide a FotoNotes workflow export document listing every template, routing rule, and automation trigger for your Nutshell admin to rebuild. Post-migration support is available for 5 business days for any data issues discovered after go-live.
Platform deep dives
FotoNotes
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 FotoNotes 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
FotoNotes: Not publicly documented.
Data volume sensitivity
FotoNotes 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 FotoNotes to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your FotoNotes 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 FotoNotes
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.