Migrate your FotoNotes data

Properties serve as the top-level container in FotoNotes. They store display-line fields that cascade down to contained work records via the container template inheritance. We migrate Properties as the parent record and preserve all display-line field values in place.

Work orders are the primary containee object — instances of a work type (inspection, maintenance, repair, audit) created under a Property. Each work order carries its own fields, photos, comments, and activity log. We map these 1:1 and preserve the parent container linkage.

Photos are the core artifact in FotoNotes. Every photo is attached to a work order or property and can be flagged by field users. We export photos in their original format with EXIF metadata intact and re-attach them to the corresponding work order record in the destination.

Vendor records represent third-party contractor organizations with their own admin and field user sub-accounts. The vendor hierarchy does not map directly to most CRM objects, so we map vendors to Companies and nest vendor users under the vendor company as contacts with the appropriate role assignment.

Field users perform inspections and work orders from a mobile app. They have a distinct permission set from portal users. We map field users to Users in the destination, applying the field-user role or equivalent, and reassign their open work order assignments accordingly.

Customers are read-only portal viewers assigned to specific projects. They can view customer reports and the activity log. We preserve the customer-to-project association and map them to a read-only contact or portal-user record in the destination.

Container and containee templates define the field schema for properties and work orders. Custom fields added via templates vary by tenant. We map custom template fields to custom properties in the destination, flagging any fields that exist only on the template definition but have no populated values.

Comments are attached to work orders via the comment modal in the web portal. Portal Admins and Managers can add comments, and field users can contribute via the mobile app. We preserve the comment body, author, and timestamp linked to the work order.

Documents can be attached at the template level or the individual work order level. Portal Admins and Managers with appropriate permissions can attach documents. We migrate all document attachments and maintain their association to the parent work order or property record.

The activity log on each work order tracks all changes including photo flags, status transitions, and field edits with timestamps and user attribution. We replicate the activity log entries as audit notes or a history object in the destination to preserve the full change chain.

Work types and tags are user-defined and customizable by Portal Admins. Tags classify work orders and can be hidden or visible per role. We map tags to labels or a multi-select custom field, preserving the full tag vocabulary and role-based visibility settings where the destination supports it.

Batch PDF reports are an admin-level feature allowing bulk export of multiple reports. The generated PDFs are system artifacts, not raw data. We extract the underlying work order data and photo references that fed the report and migrate the structured record — the PDF itself is re-generated at the destination rather than transferred as a binary.