CRM migration

Migrate from FotoNotes to Nutshell

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

FotoNotes logo

FotoNotes

Source

Nutshell

Destination

Nutshell logo

Compatibility

90%

9 of 10

objects map 1:1 between FotoNotes and Nutshell.

Complexity

BStandard

Timeline

24–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

FotoNotes logo

FotoNotes

What's pushing teams away

  • Status updates on work orders sometimes fail to sync across the web portal and mobile app, causing field supervisors to lose visibility on which properties have been completed.
  • The platform rebranded from FotoNotes to SiteCapture in 2022, and the two product names cause confusion during vendor evaluation and support escalation — existing customers on the legacy FotoNotes branding struggle to locate updated documentation and pricing pages.
  • Batch report generation is an admin-only feature, so front-line field managers who need on-demand PDF summaries must request exports from a portal admin rather than generating them independently.
  • Custom fields created via templates are per-account and not easily documented — when migrating off platform, the complete field schema requires manual enumeration from within the portal admin settings.

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

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)

maps to

Nutshell

Account

1:1
Fully supported

FotoNotes 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

maps to

Nutshell

Deal

1:1
Fully supported

Each 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

maps to

Nutshell

Custom Field Group

1:1
Fully supported

FotoNotes 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

maps to

Nutshell

Person

1:1
Fully supported

FotoNotes 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

maps to

Nutshell

Person

many:1
Fully supported

FotoNotes 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

maps to

Nutshell

File Attachment

1:1
Fully supported

FotoNotes 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

maps to

Nutshell

Note

1:1
Fully supported

FotoNotes 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

maps to

Nutshell

Activity

1:1
Fully supported

FotoNotes 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

maps to

Nutshell

User / Person Owner

1:1
Fully supported

FotoNotes 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

maps to

Nutshell

Custom Field on Person

1:1
Fully supported

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

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.

FotoNotes logo

FotoNotes gotchas

High

Container-to-contained field inheritance is implicit

Medium

Batch PDF reports are the only bulk export mechanism

Medium

Vendor sub-accounts require hierarchical mapping

Low

FotoNotes is now SiteCapture — documentation split

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

  • FotoNotes container hierarchy has no native Nutshell equivalent

    FotoNotes organizes work orders inside property containers — a single property can hold dozens of inspection records, each with its own status, priority, and custom fields. Nutshell has no parent-child deal hierarchy; deals are flat records linked to an account. FlitStack AI flattens the hierarchy by creating one deal per work order and linking every deal to the migrated account representing its parent property. You receive a mapping table showing every container-to-account and containee-to-deal link so your team can rebuild any grouping logic using Nutshell's saved views or custom report filters.

  • Custom work order fields require manual pre-creation in Nutshell

    FotoNotes work order templates define custom fields per inspection type — numeric fields for square footage, pick-list fields for condition ratings, date fields for permit expirations. Nutshell deal custom fields must be created manually in the Nutshell settings before data lands. FlitStack AI delivers a field creation checklist as part of the pre-migration plan, listing every FotoNotes template field, its data type, and the corresponding custom field name to create in Nutshell. Without this pre-work, custom field data from FotoNotes cannot be loaded into Nutshell deals.

  • Photo annotations and before/after comparison metadata are lost in migration

    FotoNotes inspection photos carry annotation layers — circled defects, drawn polygons, before/after comparison overlays — that are part of the inspection record value. Nutshell file attachments support only raw image or PDF files; annotation layers are stored in FotoNotes' proprietary format and do not export as a standard file attribute. FlitStack AI preserves photo files and captions but cannot carry annotation metadata into Nutshell. If annotation context is business-critical, export annotated PDF reports from FotoNotes before migration and link them as file attachments in Nutshell.

  • Vendor and field user role distinctions collapse in Nutshell's contact model

    FotoNotes distinguishes between Customer, Field User, Vendor Admin, and Vendor Field User — each role has different portal permissions and notification routing. Nutshell contacts do not have a role permission model; they are person records linked to an account. We map FotoNotes role types to a custom pick-list field on the person record, but Nutshell does not enforce access control based on this field. Portal admin privileges and notification routing from FotoNotes must be rebuilt as Nutshell automation rules or documented separately.

  • Batch PDF report scheduling has no Nutshell equivalent

    FotoNotes batch PDF reports are scheduled exports of multiple inspections aggregated into a single document — commonly used for monthly portfolio summaries or end-of-project deliverable packages. Nutshell does not have a native report scheduling or batch export feature at this scope. FlitStack AI cannot migrate batch report generation logic. We recommend exporting all required batch reports from FotoNotes before migration cutoff and storing them in a shared document system. Nutshell's built-in reporting and exported CSV data can serve ongoing reporting needs post-migration.

Migration approach

Six steps for a successful FotoNotes to Nutshell data migration

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

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

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

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

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

Context on both ends of the pair

FotoNotes logo

FotoNotes

Source

Strengths

  • Photo-first inspection workflow with mobile app capture and cloud sync across devices
  • Container/containee data model reduces duplicate property data across large portfolios
  • Supports seven distinct user roles including vendor admin and customer read-only access
  • Batch PDF report exports allow portfolio-level review across multiple properties at once
  • Field user mobile app works offline and syncs when connectivity is restored

Weaknesses

  • The FotoNotes-to-SiteCapture rebranding splits web presence and creates documentation gaps for legacy customers
  • Granular role-based permissions require careful mapping during migration — vendor admin and customer roles do not map directly to standard CRM roles
  • Custom work type templates vary by account, making schema extraction non-trivial without direct portal admin access
  • Status synchronization issues between web and mobile are an ongoing pain point reported in user reviews
  • No publicly documented public API means programmatic data export relies on the admin batch report feature rather than a REST endpoint
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 FotoNotes 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

    FotoNotes: Not publicly documented.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most FotoNotes-to-Nutshell migrations complete within 24–72 hours of clock time for setups under 10,000 records. The longest planning step is creating Nutshell custom fields to match FotoNotes work order templates. Larger migrations with deep container hierarchies (50+ work orders per property) or more than 50,000 total records extend to 5–7 days. The delta-pickup window adds 24–48 hours after the initial load run.

Adjacent paths

Related migrations to explore

Ready when you are

Move from FotoNotes.
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