Migrate from Planfix to Odoo CRM

Planfix Contact records map directly to Odoo res.partner. The contact's profile card fields (name, email, phone, address, company) map to typed Odoo partner fields. Custom fields on Planfix contacts migrate to res.partner custom fields created in Odoo Studio before import. We snapshot Planfix's workspace-specific field schema first so that custom contact fields are created before any partner records load. Active/archived status in Planfix maps to Odoo's active boolean on res.partner.

Planfix Project records map to Odoo project.project. Planfix's unlimited project allowance on paid tiers means we migrate all active and archived projects. Each project's custom fields (dates, status, description, manager) map to project.project fields or custom fields created in Odoo Studio. Task structure and task dependency links carry over as project.task records under each project.

Planfix Task records are the core record type and map 1:1 to Odoo project.task. We bypass the Planner view filter layer by querying tasks directly from the Planfix API endpoint, ensuring no records are missed due to visibility permissions or date filter logic. Task status, priority, assignees, checklists, comments, time logs, and file attachments all migrate as structured fields on the project.task record. The parent project reference resolves to the project.project ID computed during the project import phase.

Planfix time logs against tasks (recorded via timers or manual entry) migrate to Odoo account.analytic.line linked to the corresponding project.task. Each time log's duration, date, user attribution, and description migrate. If the destination Odoo instance does not have Timesheets (project_timesheet module) installed, time logs migrate as structured task description notes instead, and the customer can enable timesheet tracking post-migration.

File attachments on Planfix contacts, projects, and tasks migrate to Odoo ir.attachment records linked to the corresponding res.partner, project.project, or project.task. We export attachments via Planfix's template variables or direct download URL and store them in Odoo's attachment store. Files that exceed Odoo's default attachment size limit are flagged for alternative storage configuration before import.

Planfix comments on tasks and contacts migrate to Odoo mail.message records (the Discuss/message history on each record). Comment author, timestamp, and body text transfer. Mentions and emoji reactions do not carry over as these have no Odoo equivalent in the standard message model.

Planfix custom fields (text, number, date, dropdown, checkbox, File types) vary per workspace and require a schema snapshot before any record mapping begins. We query field definitions from the Planfix API to capture field type, label, and ID, then create matching Odoo custom fields via Odoo Studio or data migration field creation. Dropdown fields in Planfix become Odoo selection fields or many2one relations depending on the customer's data model choice. This step adds 3-5 business days to discovery for workspaces with more than 50 custom fields.

Planfix Workgroups (organizational units grouping users and permissions) map to Odoo crm.team records. Plan X allows up to 100 workgroups. Team membership and roles migrate as crm.team membership records. Workgroup-level permission structures in Planfix (which are Planfix-specific) do not have a direct Odoo equivalent and are documented for manual rebuild in Odoo Access Rights or Team Settings.

Planfix saved reports (built with the Planfix report builder) export as CSV or XLSX data but the saved report definition is not portable. We export the underlying data in structured CSV format for re-import into Odoo's pivot table or custom SQL reporting views. Complex reports with cross-object joins require manual rebuild in Odoo using the database view or Odoo Studio report designer. We deliver a written report inventory listing each Planfix report and its recommended Odoo equivalent.

Planfix Processes (multi-step automated sequences triggered by contact or task events) and Scripts reference Planfix-specific field IDs, action types, and execution contexts. These cannot be exported, mapped, or replayed in Odoo. We export the Process and Script configuration as a written document including trigger conditions, step definitions, action types, and conditional branches. The customer's Odoo admin or an Odoo implementation partner rebuilds these as Studio Automations or Server Actions post-migration.

Planfix Whiteboard content (block-based diagrams stored in the Whiteboard feature) has no documented export format or API access path. Whiteboard records cannot be structured for import into Odoo. We flag these as non-migratable before the migration begins and capture screenshots if the customer requires a visual record of the content.

Planfix Planner views are calendar-based task displays with user-specific saved filters, groupings, and date ranges. These are tied to the authenticated user's permissions and have no API export path. We export the underlying task data (see Task mapping) but cannot preserve personal Planner layout preferences. The Odoo Calendar and Gantt views replace Planner functionality in the destination.