Migrate from FotoNotes to Twenty CRM

FotoNotes Container records (property or project names with addresses, status, and display lines) map directly to Twenty Company records. The Company.displayName field holds the Container name; address fields map to company address fields in Twenty. If the FotoNotes Container represents a parent property in a hierarchy, the Parent Company link becomes the Twenty ParentId reference.

Each Containee work order record maps to a Twenty Opportunity linked to the parent Container's Company record via companyId. The Opportunity.name field holds the work order title; work order status maps to Opportunity.stage as a select field with FotoNotes' original status values as options. If FotoNotes has multiple work order types (e.g., Inspection, Maintenance, Repair), each type maps to a separate Opportunity record type in Twenty.

If FotoNotes runs multiple Containee templates (Inspection, Maintenance, Vendor Work) with distinct custom fields per type, those cannot all share the same Twenty Opportunity schema cleanly. FlitStack creates a WorkOrder custom object in Twenty and maps each Containee type to it, preserving the template-type field as a select (WorkOrderType__c). This avoids flattening heterogeneous custom fields onto a single Opportunity object.

FotoNotes vendor users and field users map to Twenty People records. The person's name, email, phone, and role assignment (Vendor Admin, Vendor Field User) become fields on the People record. The role assignment is stored as a custom select field (FotoNotesRole__c) for audit trail. Vendor companies themselves map to separate Company records if the vendor is an organization; individual vendor users map to People linked to that Company.

FotoNotes Customer role users (property owners or clients who can view projects via portal) map to Twenty People records with a custom flag (IsCustomerPortal__c). Their access to view shared projects is not a native Twenty construct — FlitStack preserves the customer relationship as a note on the associated Company record and recommends rebuilding read-access via Twenty's row-level permissions on the Organization plan post-migration.

FotoNotes stores photo references as CDN URLs attached to Containee work orders. These migrate to Twenty as Note records linked to the corresponding Opportunity (or WorkOrder custom object), with the original CDN URL preserved in the Note body or a custom URL field (PhotoURL__c). For inline images, FlitStack downloads and re-uploads to Twenty's file storage and updates the reference. Batch PDF reports (FotoNotes Batch Reports feature) are not migratable and are documented as a rebuild target.

FotoNotes activity log entries on Containee work orders — status changes, flag events, comment threads — map to Twenty Task records linked to the corresponding Opportunity. The Task.title field holds a summary of the activity; Task.body or the description field holds the comment text with original timestamp and user attribution preserved. This gives teams the full work-order activity timeline in Twenty's record history.

FotoNotes Container records support display lines (custom fields per template) that hold property-specific data — for example, property type, inspection frequency, or billing code. These migrate as custom fields on the Twenty Company object. FlitStack creates each custom field in Settings → Data Model before the import run and maps the field values during the CSV load. Field type mapping follows FotoNotes' field-type definitions (text, number, date, select).

Containee work order records carry custom fields specific to each work order template — inspection findings, priority level, scheduled date, assigned vendor. These migrate as custom fields on the Twenty Opportunity (or WorkOrder custom object) based on the Containee template type. FlitStack creates the fields in Twenty before import and applies value-level mapping for select/multi-select fields using FotoNotes' original pick-list values as options.

FotoNotes supports nested Container hierarchies (parent properties with child sub-properties or project phases). Twenty Company's ParentId field holds the parent Company reference. FlitStack resolves the hierarchy during export: the parent Container must migrate as a Company first so its ID is available as a foreign key when child Containers are loaded. Circular or orphan references are flagged before migration runs.

FotoNotes assigns users to Containers and Work Orders by user ID (Manager, Field User, assigned vendor). Twenty resolves ownership via WorkspaceMember records matched by email. FlitStack performs an email match against Twenty's member list before migration: matched users get their records assigned directly; unmatched users are flagged for the admin to invite to Twenty first, with a fallback assignee configured before the full run.

FotoNotes Container and Containee templates define which fields appear per work order type — this is a schema-level configuration with no export path. FlitStack documents the full template schema (field names, types, required flags) as a setup guide for Twenty administrators, including which fields map to Twenty's standard objects versus custom fields. This documentation is delivered alongside the migration runbook.