Migrate from FieldPro to Odoo CRM

FieldPro outlets are physical retail or field locations with name, address, GPS, and category. These map directly to Odoo res.partner records with partner_type='contact' and industry category matching. GPS latitude/longitude stored in custom float fields on partner record since Odoo has no native geo field.

FieldPro contacts (sales reps or outlet contacts) map to Odoo res.partner records, preserving address and contact details. If a contact also owns the outlet, a parent_id link points to the corresponding outlet partner, maintaining the hierarchical relationship. Email, phone, and title fields transfer directly, and any custom contact attributes become custom fields on the partner record.

FieldPro visit records, which include timestamp, agent, outlet, and outcome, map to Odoo CRM activities (mail.activity). The visit outcome (completed, skipped, rescheduled) maps to the activity_type selection, and the outlet reference becomes the activity’s res_id linking to the outlet’s res.partner. Duration and notes become activity description fields, with additional custom fields capturing structured outcome data if needed.

FieldPro route assignments with sequence, assigned agent, and date have no native Odoo equivalent. We map each route to a project.task record tagged by agent and date, with task name = route name and description capturing the outlet sequence. A custom project or tag distinguishes route-grouped tasks from regular project work.

FieldPro orders captured in the field map to Odoo sale.order records linked to the outlet’s res.partner as the customer. Order lines transfer to sale.order.line with product (mapped to product.template), quantity, and price. Order status (draft, confirmed, fulfilled) maps to Odoo sale.order state values via value mapping, ensuring consistent workflow progression.

FieldPro product catalog entries map to Odoo product.template, transferring product name, SKU, unit of measure, and sales price directly. If FieldPro defines product categories, those map to Odoo product.category records for hierarchical organization, allowing the same categorization structure to be replicated in the target system.

FieldPro agents (field workers) are matched to Odoo users by email address. FlitStack flags unmatched agents before migration so they can be invited to Odoo. Agent active status and team assignment map to Odoo user active flag and crm.team membership.

FieldPro task records (field assignments, follow‑ups) map to Odoo project.task linked to the outlet’s res.partner. Task status (pending, completed) maps to Odoo stage, and priority aligns with the Odoo priority field (0‑4 scale). Custom task attributes from FieldPro become custom fields on the project.task model, preserving all original data.

FieldPro custom fields on outlets (beyond name, address, GPS) require Odoo custom fields created via Odoo Studio or data migration. Each custom field type (char, selection, float, integer) maps to the corresponding Odoo field type. Selection-type custom fields need value_mapping for pick-list consistency.

FieldPro visit outcomes (sold, no order, competitor seen) and check‑in timestamps become custom fields on Odoo mail.activity, such as x_outcome and x_checkin_time. This preserves the structured outcome data that would otherwise be lost if entered only as free‑text notes, maintaining reporting continuity across the migration.