---
title: "FotoNotes to Salesforce Migration: Field Mapping & Rollback"
description: "Migrate FotoNotes to Salesforce with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/crm/fotonotes/to/salesforce-sales-cloud"
---

# FotoNotes to Salesforce migration

Moving from FotoNotes to Salesforce Sales Cloud maps a field-inspection SaaS into a full CRM. FlitStack AI converts FotoNotes properties and work orders into Salesforce custom objects — preserving photo counts, inspection status, and the container-relationship hierarchy — so your Salesforce org holds the complete inspection data set alongside Accounts, Contacts, and Opportunities from day one.

Short answer

FlitStack AI migrates custom object: property\_\_cs, custom object: work\_order\_\_cs, custom pick-list on work\_order\_\_c: template\_name\_\_cs, standard object: contact + role\_type\_\_c custom fields and standard object: contact + salesforce user lookups from FotoNotes to Salesforce, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 48–96 hours for under 25,000 records.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See the field mapping →](https://flitstack.ai/migrations/crm/fotonotes/to/salesforce-sales-cloud#field-mapping)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source FotoNotes ![](https://flitstack.ai/platforms-trim/fotonotes.webp)

Destination Salesforce ![](https://flitstack.ai/platforms-trim/salesforce-sales-cloud.webp)

Custom object: Property\_\_c Custom object: Work\_Order\_\_c Custom pick-list on Work\_Order\_\_c: Template\_Name\_\_c Standard object: Contact + Role\_Type\_\_c custom field Standard object: Contact + Salesforce User lookup

Mapped field by field · sample run · one-click rollback

## What moves from FotoNotes to Salesforce?

FotoNotes is a property-inspection and field-operations platform built around three core constructs: Property (the container, analogous to a physical asset or site), Work Order (the containee, an inspection or maintenance task with photos and status), and Template (the inspection form structure).

Read the full summary

It stores roles (Portal Admin, Manager, Field User, Customer, Vendor) that are distinct from person records. Salesforce Sales Cloud has no native inspection or work-order object. All FotoNotes inspection data — work order status, photo count, template name, priority, due date, property relationships, and geolocation — requires Salesforce custom objects (Property\_\_c and Work\_Order\_\_c) with type-aware custom fields. Core person records (contacts, customers, vendors) migrate to standard Salesforce Contact and Account objects with a Role\_Type\_\_c custom field identifying the FotoNotes role. We map FotoNotes Properties to Salesforce custom Property\_\_c, Work Orders to custom Work\_Order\_\_c with a Property\_\_c lookup to preserve the container hierarchy, and Template names to a custom pick-list on Work\_Order\_\_c. Original create dates and owner timestamps migrate to custom datetime fields since Salesforce sets CreatedDate at insertion time. Photo files re-upload to Salesforce Files; photo metadata (caption, flags) requires a custom Photo\_Metadata\_\_c text field because Salesforce Files attachments do not natively preserve inspection annotations. Workflows, batch reports, display-line configurations, and role-permission sets do not migrate — they are exported as reference documents for rebuild in Salesforce Flow, Reports, and profile assignments. Our migration runs via FotoNotes read API and Salesforce Bulk API, with a 24–48h delta-pickup window capturing in-flight changes during cutover.

custom\_field\_required

### Property (Container) → Custom object: Property\_\_c

FotoNotes Property is a container record for a physical site or asset.

How it maps

Salesforce has no standard Property object. FlitStack creates Property\_\_c with custom fields for property type, status, address components (mapped to the standard compound BillingAddress on Account or a separate Address\_\_c custom object), and original FotoNotes ID preserved as Source\_System\_ID\_\_c for delta-run deduplication.

custom\_field\_required

### Work Order (Containee) → Custom object: Work\_Order\_\_c

FotoNotes Work Order is the primary inspection record.

How it maps

It maps to a custom Work\_Order\_\_c object because Salesforce has no native work-order entity in Sales Cloud. The object holds inspection details, template name, status, priority, photo count, due date, geolocation, and a lookup to Property\_\_c. Original FotoNotes create date and last-modified date migrate to custom datetime fields since Salesforce CreatedDate and LastModifiedDate reflect migration insertion time.

custom\_field\_required

### Template (Inspection form structure) → Custom pick-list on Work\_Order\_\_c: Template\_Name\_\_c

FotoNotes Templates define the inspection form structure and field set for a work order type.

How it maps

Template names migrate to a custom pick-list field Template\_Name\_\_c on Work\_Order\_\_c so the association is preserved. Conditional field logic and required-section rules within a template have no Salesforce equivalent and must be rebuilt as Salesforce page layout configurations or Flow decisions by your admin.

direct

### Customer / Owner (person) → Standard object: Contact + Role\_Type\_\_c custom field

FotoNotes Customers are person records who can view assigned projects.

How it maps

They map directly to Salesforce Contact. A Role\_Type\_\_c custom pick-list field (value: 'Customer') identifies the FotoNotes role type on each Contact record. If a Customer shares an email with an existing FotoNotes Contact, both records merge to one Contact to prevent duplicates.

direct

### Vendor (person) → Standard object: Contact + Role\_Type\_\_c custom field

FotoNotes Vendors are third-party company admins or field users assigned to work orders.

How it maps

They map to Salesforce Contact with Role\_Type\_\_c set to 'Vendor'. Vendor-specific fields (company name, services offered) map to Contact Account lookup where a vendor company Account exists, or to custom fields on Contact if no Account is present.

transformed

### FotoNotes User (internal staff) → Standard object: Contact + Salesforce User lookup

Internal FotoNotes users (Portal Admins, Managers, Field Users) are resolved by email match against existing Salesforce Users.

How it maps

Unmatched users are flagged before migration — your team either creates a Salesforce User or assigns records to a fallback owner. FotoNotes user records also surface as Contacts with Role\_Type\_\_c = 'Internal Staff' so the full person record exists in Salesforce even if no login license is assigned.

******What moves 12 objects

FotoNotes Salesforce

- Property Custom object: Property\_\_c transformed
- Work Order Custom object: Work\_Order\_\_c transformed
- Template Custom pick-list on Work\_Order\_\_c: Template\_Name\_\_c transformed
- Customer Standard object: Contact 1:1
- Vendor Standard object: Contact 1:1
- FotoNotes User Standard object: Contact transformed

\+ 6 more in the mapping below

## How FotoNotes and Salesforce differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

| Dimension             | FotoNotes                                                                                                                                                            | Salesforce                                                                                                                                                                                                      |
| --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Core focus            | FotoNotes is a property-inspection and field-operations platform built for property managers, field crews, and vendors managing work orders and photo documentation. | Salesforce Sales Cloud is a full CRM for lead management, opportunity tracking, and sales automation — it has no native work-order or inspection object.                                                        |
| Work order object     | FotoNotes Work Order is a first-class containee record with status, template, priority, photo count, and due date — it is the primary unit of inspection activity.   | Salesforce has no Work Order object in standard Sales Cloud — requires custom Work\_Order\_\_c object with custom fields for status, priority, photo count, and template name.                                  |
| Property relationship | FotoNotes uses a container/containee hierarchy: Property holds multiple Work Orders. N:1 and 1:N relationships are both supported.                                   | Salesforce Work\_Order\_\_c uses a lookup to Property\_\_c. Single-property assignments map directly; multi-property assignments require a primary lookup plus secondary property field or custom multi-select. |
| Photo handling        | FotoNotes stores photos with captions, flag annotations, and geolocation. Batch PDF reports aggregate multiple work orders into a single export.                     | Salesforce Files re-upload photos but strip FotoNotes-specific metadata. Batch reports must be rebuilt using Salesforce Reports or a BI tool.                                                                   |
| Automation            | FotoNotes supports work-order assignment rules and status-update triggers that run inside the inspection workflow.                                                   | Salesforce Flow and Process Builder provide equivalent automation but require manual rebuild — FotoNotes automation does not transfer.                                                                          |
| User roles            | FotoNotes defines seven role types (Portal Admin, Manager, User, Field User, Customer, Vendor Admin, Vendor Field User) that govern access and permissions.          | Salesforce profiles and permission sets govern access — FotoNotes role types do not map natively. They migrate as a custom Role\_Type\_\_c pick-list on Contact.                                                |
| Reporting             | FotoNotes Batch Reports export aggregated inspection data across multiple work orders. Display lines configure which fields appear in project views.                 | Salesforce Reports and Dashboards build from custom report types on Work\_Order\_\_c. Batch report logic must be rebuilt — FlitStack exports metadata for reference.                                            |
| API rate limits       | FotoNotes API is not published with documented rate limits for migration purposes.                                                                                   | Salesforce Enterprise Edition enforces 100,000 daily API requests plus 1,000 per user license. Bulk API handles large batches (10,000 records per batch) to stay within limits.                                 |

## FotoNotes to Salesforce field mapping

The 30 most-used fields of 39 mapped for this pair. Custom fields are added from your own schema during scoping. [Download the full mapping (CSV) ↓](https://flitstack.ai/migrations/crm/fotonotes/to/salesforce-sales-cloud.csv) or open it in the [field mapping template](https://flitstack.ai/tools/field-mapping-template).

******Field mapping 5 shown

FotoNotes Salesforce

1. `property_name` Property `Name` Property\_\_c
2. `property_type` Property `Property_Type__c` Property\_\_c
3. `status` Property `Status__c` Property\_\_c
4. `street_address` Property `BillingStreet` Account
5. `city` Property `BillingCity` Account

| FotoNotes field                          | Salesforce field                               | Mapping                 | Note                                                                                                                           |
| ---------------------------------------- | ---------------------------------------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| `Property.property_name`                 | `Property__c.Name`                             | direct                  |                                                                                                                                |
| `Property.property_type`                 | `Property__c.Property_Type__c`                 | direct                  |                                                                                                                                |
| `Property.status`                        | `Property__c.Status__c`                        | direct                  |                                                                                                                                |
| `Property.street_address`                | `Account.BillingStreet`                        | transformed             | Property address migrates to an Account record; Property\_\_c links to Account via AccountId lookup.                           |
| `Property.city`                          | `Account.BillingCity`                          | direct                  |                                                                                                                                |
| `Property.state`                         | `Account.BillingState`                         | direct                  |                                                                                                                                |
| `Property.zip_code`                      | `Account.BillingPostalCode`                    | direct                  |                                                                                                                                |
| `Property.country`                       | `Account.BillingCountry`                       | direct                  |                                                                                                                                |
| `Property.latitude`                      | `Property__c.Latitude__c`                      | direct                  | Custom decimal field storing GPS latitude from FotoNotes geolocation.                                                          |
| `Property.longitude`                     | `Property__c.Longitude__c`                     | direct                  | Custom decimal field storing GPS longitude from FotoNotes geolocation.                                                         |
| `Property.created_date`                  | `Property__c.Original_Create_Date__c`          | custom\_field\_required | Salesforce CreatedDate reflects migration insertion time. Original FotoNotes create date preserved in custom datetime field.   |
| `Property.last_modified_date`            | `Property__c.Original_Last_Modified_Date__c`   | custom\_field\_required | Original last-modified timestamp from FotoNotes preserved as a custom datetime field.                                          |
| `Property.fotonotes_id`                  | `Property__c.Source_System_ID__c`              | custom\_field\_required | FotoNotes internal ID stored on Property\_\_c for traceability and delta-run de-duplication.                                   |
| `Work Order.work_order_name`             | `Work_Order__c.Name`                           | direct                  |                                                                                                                                |
| `Work Order.property_id`                 | `Work_Order__c.Property__c`                    | direct                  | Work\_Order\_\_c.Property\_\_c is a lookup to Property\_\_c — maps FotoNotes container/containee relationship.                 |
| `Work Order.status`                      | `Work_Order__c.Status__c`                      | value\_mapping          | Status values mapped value-by-value. Custom FotoNotes status values require pick-list addition in Salesforce before migration. |
| `Work Order.priority`                    | `Work_Order__c.Priority__c`                    | value\_mapping          | Priority values mapped value-by-value to custom pick-list. Custom priority values require pick-list extension.                 |
| `Work Order.template_name`               | `Work_Order__c.Template_Name__c`               | custom\_field\_required | Custom pick-list field storing the FotoNotes template name associated with this work order.                                    |
| `Work Order.description`                 | `Work_Order__c.Description`                    | direct                  |                                                                                                                                |
| `Work Order.due_date`                    | `Work_Order__c.Due_Date__c`                    | direct                  |                                                                                                                                |
| `Work Order.completed_date`              | `Work_Order__c.Completed_Date__c`              | direct                  |                                                                                                                                |
| `Work Order.inspection_date`             | `Work_Order__c.Inspection_Date__c`             | direct                  |                                                                                                                                |
| `Work Order.photo_count`                 | `Work_Order__c.Photo_Count__c`                 | direct                  |                                                                                                                                |
| `Work Order.assigned_user_email`         | `Work_Order__c.OwnerId`                        | transformed             | Owner resolved by email match to Salesforce User. Unmatched owners flagged before migration.                                   |
| `Work Order.created_date`                | `Work_Order__c.Original_Create_Date__c`        | custom\_field\_required | Original FotoNotes create date preserved as custom datetime since Salesforce CreatedDate is set at migration time.             |
| `Work Order.last_modified_date`          | `Work_Order__c.Original_Last_Modified_Date__c` | custom\_field\_required | Original last-modified timestamp preserved in custom datetime field for audit continuity.                                      |
| `Work Order.fotonotes_id`                | `Work_Order__c.Source_System_ID__c`            | custom\_field\_required | FotoNotes internal ID stored for traceability and delta-run de-duplication.                                                    |
| `Contact (FotoNotes Contact).first_name` | `Contact.FirstName`                            | direct                  |                                                                                                                                |
| `Contact (FotoNotes Contact).last_name`  | `Contact.LastName`                             | direct                  |                                                                                                                                |
| `Contact (FotoNotes Contact).email`      | `Contact.Email`                                | direct                  |                                                                                                                                |

## What to watch for in a FotoNotes to Salesforce migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

high

### Photo metadata (captions, flags, annotations) has no Salesforce Files equivalent

FotoNotes photos carry inspection-specific metadata: caption text entered by the field user, flag annotations marking defects or areas of concern, and geolocation beyond street address.

How we handle it

Salesforce Files (ContentDocument / ContentVersion) store the file binary and basic title but do not natively preserve FotoNotes-specific photo metadata fields. FlitStack re-uploads photos as Salesforce Files preserving the original binary and title, but caption text and flag annotations migrate to a custom Photo\_Metadata\_\_c long-text field on the associated Work\_Order\_\_c record. Your team should review Photo\_Metadata\_\_c after migration to confirm all annotation data is legible — in some cases, the metadata references require manual re-entry in Salesforce if the field user needs it inside the record detail page.

high

### Multi-property work orders require a primary assignment decision before migration

FotoNotes container/containee model supports a work order that spans multiple properties — the same inspection task can be linked to two or more Property records simultaneously.

How we handle it

Salesforce Work\_Order\_\_c uses a single Property\_\_c lookup field, which enforces a strict one-to-one parent relationship by default. FlitStack surfaces every FotoNotes work order with multiple parent properties during the pre-migration audit. The primary property maps to Work\_Order\_\_c.Property\_\_c; additional properties are stored in a Secondary\_Properties\_\_c custom multi-select text field. Your admin must decide and document the primary assignment rule (most-recently-modified property, largest property by square footage, etc.) before migration runs — this is a stakeholder decision, not an automated one.

medium

### Vendor and customer roles require contact deduplication before migration

FotoNotes stores vendors and customers as separate role types distinct from contact records — a vendor company admin is a Vendor role even if they also have an email in the system as a customer contact.

How we handle it

Salesforce Contact is a single person record with no native role-type distinction. During migration, vendors and customers without a matching FotoNotes contact email are created as new Salesforce Contacts with Role\_Type\_\_c set to 'Vendor' or 'Customer'. Where a vendor or customer email matches an existing FotoNotes contact, the records merge to a single Contact with the role type appended. This deduplication logic prevents duplicate Contact creation but requires stakeholder sign-off on the merge rule before migration runs.

medium

### Batch report logic does not transfer — only metadata migrates

FotoNotes Batch Reports aggregate inspection data across multiple work orders into a single PDF export, configured with specific filters, sort orders, and column selections.

How we handle it

Salesforce Reports aggregate via report types and saved filters that are configured entirely inside Salesforce — they do not carry over from any external system. FlitStack exports batch report metadata (report name, filter criteria, creation date, associated work order IDs) into a custom Batch\_Report\_Reference\_\_c object so the existence and scope of each FotoNotes report is documented. The report logic itself must be rebuilt from scratch using Salesforce Reports & Dashboards or a third-party BI tool. This is disclosed upfront so stakeholders can budget the rebuild effort and decide which reports to prioritize.

low

### Template conditional logic and required-field rules require manual rebuild

FotoNotes Templates define the structure of a work order type — which fields appear, which are required, which sections are conditional on prior answers.

How we handle it

Salesforce has no template engine for custom objects that enforces conditional field visibility or cross-field validation at the form level. Template names migrate as a Template\_Name\_\_c pick-list field on Work\_Order\_\_c so the association is recorded, but the conditional logic (e.g., 'show roof-inspection section only if property\_type = residential') must be rebuilt. Your Salesforce admin can implement this using page layout field visibility rules, required-field configurations, or Flow screens — but FotoNotes template rules do not transfer as executable logic.

## How the migration runs

1. ### Audit FotoNotes data inventory and schema

   Before migration begins, FlitStack AI inventories all FotoNotes objects accessible via the API: Property records, Work Order records, Template definitions, Batch Reports, User accounts, Vendor/Customer contact records, and attachments.

   What this step covers

   This audit produces a record count per object, a schema inventory listing all custom fields and pick-list values in FotoNotes, and a log of any work orders with multiple parent properties. The audit also identifies the oldest create dates so original timestamps can be flagged for preservation during mapping. This step typically takes 2–3 business days and is completed before any Salesforce schema work begins.

2. ### Set up Salesforce custom objects and fields

   With the FotoNotes schema inventory complete, FlitStack creates the Property\_\_c and Work\_Order\_\_c custom objects in your Salesforce sandbox, adds all required custom fields (Status\_\_c, Priority\_\_c, Template\_Name\_\_c, Photo\_Count\_\_c, Latitude\_\_c, Longitude\_\_c, Original\_Create\_Date\_\_c, Source\_System\_ID\_\_c, Photo\_Metadata\_\_c, etc.), and establishes the Property\_\_c → Work\_Order\_\_c lookup relationship.

   What this step covers

   If your org already has a Property\_\_c or Work\_Order\_\_c object from a prior implementation, FlitStack appends fields to the existing object rather than creating duplicates. Pick-list values for Status\_\_c and Priority\_\_c are populated from FotoNotes' actual status and priority values identified in the audit. This step runs in a Salesforce sandbox first; production schema changes are applied after sample migration sign-off.

3. ### Resolve FotoNotes users and vendors by email match

   FotoNotes users and vendor contacts are matched against existing Salesforce Users and Contacts by email address.

   What this step covers

   Unmatched FotoNotes users are flagged in a pre-migration report with their FotoNotes role type and email — your team either creates a corresponding Salesforce User before migration or assigns those records to a designated fallback owner. Vendor and customer contacts without a matching Salesforce Contact are created as new Contact records with Role\_Type\_\_c populated. This resolution step prevents orphaned Work\_Order\_\_c records and ensures every migrated record has an OwnerId or assigned Contact before the full migration runs.

4. ### Run a sample migration with field-level diff

   A representative slice migrates first — typically 50–200 records spanning properties, work orders, contacts, and a sample photo attachment.

   What this step covers

   FlitStack generates a field-level diff between the source FotoNotes export and the destination Salesforce records so you can verify that Work\_Order\_\_c status and priority values mapped correctly, container relationships resolved to the right Property\_\_c record, owner resolution found matches or flagged correctly, and photo files attached to the correct Work\_Order\_\_c. Sample migration sign-off is required before the full production run commits.

5. ### Full migration with delta-pickup and one-click rollback

   The full migration runs against your Salesforce production org.

   What this step covers

   A delta-pickup window (typically 24–48 hours after the main run) captures any FotoNotes properties, work orders, or photos created or modified during the cutover window — your team keeps working in FotoNotes throughout. FlitStack maintains an audit log of every insert, update, and error at the record and field level. If reconciliation finds discrepancies (missing records, incorrect field values, broken container relationships), one-click rollback reverses all migration operations and restores Salesforce to its pre-migration state. You are never committed to a migration that did not land cleanly.

![](https://flitstack.ai/platforms/fotonotes.png) FotoNotes ![](https://flitstack.ai/platforms/salesforce-sales-cloud.svg) Salesforce

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · Salesforce Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**48–96 hours for under 25,000 records** Typical, smaller accounts

**7–14 days for 100,000+ records or heavy custom-template usage** Large or heavily customised accounts

FotoNotes to Salesforce Sales Cloud migrations land in the middle of our pricing range. Record volumes are typically moderate — property and work order counts rarely reach the scale of full CRM migrations. The cost driver is schema complexity: every FotoNotes inspection field that has no Salesforce standard equivalent requires a custom field on Property\_\_c or Work\_Order\_\_c, and the container/containee relationship requires a custom lookup with a multi-property handling plan. Custom template names, FotoNotes-specific status values, photo metadata, and role-type classification all add field-creation and value-mapping work. The upper end of the range applies when FotoNotes inventories exceed 50,000 records with more than 30 custom fields or complex multi-property work order assignments requiring stakeholder decisions before migration can proceed. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for FotoNotes to Salesforce →](https://flitstack.ai/contact)

## Why teams move from FotoNotes to Salesforce

- FotoNotes handles property inspections and field work orders, but it is not a CRM — leads, opportunities, and customer accounts need a separate system. As the business grows, teams end up running FotoNotes alongside another CRM, duplicating contact records and losing visibility. Consolidating onto Salesforce Sales Cloud eliminates that split and gives one platform for the entire revenue cycle, from property inspection through deal close.
- FotoNotes has limited native integrations with ERP, accounting, and back-office systems. Businesses scaling past 5,000 properties or 50 field users increasingly need Salesforce's AppExchange ecosystem and native ERP connectors to sync financial data, customer accounts, and supply-chain records without manual re-entry.
- FotoNotes batch reports aggregate inspection data across properties, but building custom inspection analytics that combine work order status, photo evidence, and team performance requires exporting to a separate BI tool. Salesforce Reports and Dashboards built on custom Work\_Order\_\_c objects deliver the same or deeper insight directly inside the CRM without leaving the platform.
- FotoNotes does not offer workflow automation for complex business rules — assignment routing, approval chains, and conditional status updates require manual handling or third-party connectors. Salesforce Flow and Process Builder provide enterprise-grade automation, though FotoNotes workflow definitions must be rebuilt rather than transferred.

Questions, answered

## FotoNotes to Salesforce migration questions

How long does a FotoNotes to Salesforce migration take?

Most FotoNotes-to-Salesforce migrations complete in 48–96 hours of clock time for under 25,000 records. Larger inventories with 100,000+ work orders, complex multi-property relationships, or heavy custom template usage extend to 7–14 days. FotoNotes data tends to be moderate in volume but high in schema complexity because inspection metadata does not map to standard CRM fields — the Salesforce custom object and field design step is typically the longest planning phase before any data moves.

Will my FotoNotes work order assignment workflows migrate to Salesforce Flow?

No. FlitStack AI migrates data and schema only — work order assignment rules, status-update triggers, and notification workflows built in FotoNotes do not transfer to Salesforce. They must be rebuilt using Salesforce Flow, Process Builder, or Apex triggers. We export your FotoNotes workflow definitions as a reference document listing every active workflow, its trigger conditions, and assigned actions so your Salesforce admin has a complete rebuild specification without needing to re-audit FotoNotes from scratch.

What does a FotoNotes Work Order become in Salesforce?

A FotoNotes Work Order migrates to a custom Work\_Order\_\_c object in Salesforce Sales Cloud. Inspection details, photo count, work order status, template name, priority, due date, completed date, and create/update timestamps all map to custom fields on Work\_Order\_\_c. The Work\_Order\_\_c links to a Property\_\_c custom object via a Property\_\_c lookup field, preserving the FotoNotes container/containee hierarchy. Original timestamps from FotoNotes are stored in custom datetime fields because Salesforce sets CreatedDate at migration insertion time.

Can I migrate FotoNotes custom templates to Salesforce?

FotoNotes templates define the structure and field set for a work order type — which sections appear, which fields are required, and conditional visibility rules. Template names migrate as a custom pick-list field (Template\_Name\_\_c) on Work\_Order\_\_c so the association is recorded. Conditional field logic (e.g., show roof section only for residential property types) has no Salesforce equivalent and must be rebuilt manually. Your Salesforce admin can implement conditional visibility using page layout field configurations, required-field rules, or Flow screen elements.

How does the FotoNotes container-relationship hierarchy map to Salesforce?

FotoNotes uses a container/containee model where a Property holds multiple Work Orders. This maps to a Property\_\_c → Work\_Order\_\_c lookup relationship in Salesforce. Single-property work orders map directly — Work\_Order\_\_c.Property\_\_c points to the correct Property\_\_c record. Where a single work order spans multiple FotoNotes properties, FlitStack stores the primary property in the Property\_\_c lookup and additional properties in a Secondary\_Properties\_\_c multi-select text field. Your admin must confirm the primary assignment rule (most-recently-modified property, largest property, etc.) before migration runs.

Does the migration affect my FotoNotes account during cutover?

No. FlitStack AI uses scoped read access on FotoNotes — your team continues working in FotoNotes throughout the migration window with no service interruption. A delta-pickup window of 24–48 hours after the main migration run captures any properties, work orders, or photos created or modified during the cutover period. This ensures Salesforce reflects FotoNotes' final state at go-live without gaps from records created or updated mid-transition. After delta-pickup completes, your team switches to Salesforce and FotoNotes access can be decommissioned.

What data will not transfer from FotoNotes to Salesforce?

Core data — work orders, properties, contacts, vendors, and photo files — migrates fully. FotoNotes-specific attributes with no Salesforce equivalent include template conditional logic (required-section rules, conditional field visibility), FotoNotes-specific status values and flag-setting metadata on individual photos (captions and defect flags migrate to a reference text field but not as structured data), geolocation coordinates that exceed standard address precision (latitude and longitude store in custom decimal fields but without map-native display), and batch report filters and sort configurations (only report metadata migrates; the report logic must be rebuilt). These gaps are documented in the migration plan so your team can assess rebuild priorities.

## Related migrations

[![](https://flitstack.ai/platforms-trim/salesforce-sales-cloud.webp) Migrate to **Salesforce** Every source we move into Salesforce, native options and the checklist. Guide, checklist & sources](https://flitstack.ai/migrations/crm/salesforce-sales-cloud)

### [Salesforce implementation](https://flitstack.ai/services/salesforce-implementation)

[Set up Salesforce and migrate into it as one engagement.](https://flitstack.ai/services/salesforce-implementation)

[See the service →](https://flitstack.ai/services/salesforce-implementation) [**Housecall Pro to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/housecall-pro/to/salesforce-sales-cloud) [**Daylite to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/daylite/to/salesforce-sales-cloud) [**Convertkit to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/convertkit/to/salesforce-sales-cloud) [**HoneyBook to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/honeybook/to/salesforce-sales-cloud) [**Customer.io to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/customer-io/to/salesforce-sales-cloud) [**monday CRM to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/monday-crm/to/salesforce-sales-cloud)

## Sources: official documentation

1. [Custom Field Attributes — Salesforce Help (External ID)](https://help.salesforce.com/s/articleView?id=platform.custom_field_attributes.htm)
2. [Increase Limit of Salesforce Big Object Storage Allocation — Salesforce Help](https://help.salesforce.com/s/articleView?id=000380434\&type=1)
3. [Uploading Activity data to Salesforce — Salesforce Stack Exchange](https://salesforce.stackexchange.com/questions/15694/uploading-activity-data-to-salesforce)
4. [Sandboxes — Staging Environments for Customizing and Testing](https://resources.docs.salesforce.com/latest/latest/en-us/sfdc/pdf/deploy_sandboxes.pdf)
5. [Case Comment STRING\_TOO\_LONG — Salesforce Stack Exchange](https://salesforce.stackexchange.com/questions/44763/case-comment-error-string-too-long-body-data-value-too-large)
6. [Salesforce Data Migration: 7 Challenges and How to Solve Them — DEV](https://dev.to/prince_6a5fbc059971cef8c8/salesforce-data-migration-7-challenges-and-how-to-solve-them-3bb7)
7. [Salesforce Duplicate Management — Salesforce Stack Exchange](https://salesforce.stackexchange.com/questions/151012/salesforce-duplicate-management-importing-duplicates)

Get a quote

## Moving from FotoNotes to Salesforce?

Tell us roughly how many records and objects you have. We scope the mapping and the Salesforce setup with you, then send a quote.

[Get a quote](https://flitstack.ai/contact)
