Migrate from FotoNotes to Odoo CRM

FotoNotes containers (projects) map to Odoo crm.lead records. A custom x_Property_Container__c char field preserves the original FotoNotes container name so the parent-child relationship is queryable within Odoo. Container status maps to crm.stage by matching FotoNotes status labels to Odoo stage names.

FotoNotes work orders map to Odoo crm.lead records. The parent container ID is stored in x_Parent_Container_ID__c to reconstruct the project hierarchy in Odoo. Work order type (e.g., inspection, maintenance) maps to a custom x_Work_Order_Type__c pick-list on the lead record. The due_date from the work order populates date_deadline, and assigned user emails are resolved to Odoo res.users login identifiers to set user_id.

FotoNotes property records map directly to Odoo res.partner records. Property name becomes partner name, street/address fields map field-for-field, and a custom x_FotoNotes_Property_ID__c field stores the source FotoNotes ID for delta-run de-duplication. City, state_id, zip, and country_id are transferred to Odoo partner columns, while phone and email are stored in the partner phone and email fields. The ID field also enables the migration process to skip duplicate properties on subsequent runs.

FotoNotes vendor contacts (Vendor Admin and Vendor Field User roles) map to res.partner records with vendor=True set. The full FotoNotes role label is stored in x_FotoNotes_Roles__c so the migration plan can specify which Odoo user groups each role maps to on the Odoo side.

FotoNotes customer-role contacts map to Odoo res.partner with customer=True. Customer-specific fields such as the can_view_reports flag are migrated as custom boolean fields on the partner record, preserving the original FotoNotes permission. The FotoNotes customer flag is stored in x_Is_FotoNotes_Customer__c to identify the contact source. Email, phone, and street address are transferred to the partner’s fields, and any role labels are recorded in x_FotoNotes_Roles__c for Odoo access-group assignment.

FotoNotes inspection templates have no Odoo CRM equivalent — they define required fields, approval chains, and form structure. FlitStack exports each template's field definitions as a JSON schema file and delivers it alongside the migration so your Odoo admin can recreate field sets in Studio.

FotoNotes batch reports (multi-project PDF exports) have no Odoo equivalent. We export the batch report configuration as CSV with record IDs and timestamps so your team can rebuild scheduled reporting in Odoo using its built-in report designer or a BI connector.

FotoNotes inspection photos and flagged images migrate to Odoo ir.attachment linked to the corresponding crm.lead (work order) or res.partner record. Each file is downloaded from FotoNotes storage, Base64-encoded, and POSTed to Odoo's /web/binary/attachment/file endpoint. Files over 25MB are split before upload.

FotoNotes internal users (Portal Admin, Manager, User, Field User) are matched to Odoo res.users by email address. Unmatched users are flagged before migration so your Odoo admin can create accounts first. FotoNotes role names are noted in the migration plan for Odoo access-group assignment.

FotoNotes records status-change timestamps in its activity log. These translate to Odoo mail.message records on the crm.lead, preserving the original timestamp, the user who made the change, and the old/new status values. Body text is formatted as a readable activity note.

FotoNotes services and work-order types have no direct Odoo equivalent. We create a custom pick-list field x_Work_Service_Type__c on crm.lead and map each FotoNotes service name to a corresponding pick-list value, preserving the drop-down semantics your team uses to categorize work.

FotoNotes work order comments migrate as Odoo mail.message records with message_type='comment', attached to the corresponding crm.lead. The timestamp of each comment is stored in the mail.message date field to preserve order. Author is resolved by email match to res.users; if unmatched, the author name is stored in the body as plain text. After migration, comments appear in the lead’s chatter and can be viewed in the Odoo UI alongside history.