Migrate from Podio to Odoo CRM

Podio workspaces map to Odoo Projects (if project-related work is in scope) or are treated as data containers whose apps are migrated individually to CRM models. Workspace-level member lists become Odoo Users or Followers on the relevant records. Workspace settings and custom workspace-level fields migrate as configuration metadata documented separately for manual setup.

Podio apps configured as contact repositories map to Odoo res.partner. The app's custom fields (name, email, phone, organization, title, address) map to Odoo standard fields (display_name, email, phone, mobile, function, street/city/country). Podio reference fields linking to organization apps map to Odoo Many2one partner_id on related records. Any unmapped custom contact fields are created as ir.model.fields (char, text, selection, or many2one) before migration.

Podio apps storing organizations or companies map to Odoo res.company for internal company records or res.partner with is_company=True for external organizations. The Odoo is_company flag is set during import based on the Podio app type designation. Organization address, industry, website, and revenue fields map to their Odoo equivalents; custom fields migrate as partner-level custom fields.

Podio apps used to track sales opportunities map to Odoo crm.lead. Podio deal stage values map to Odoo stage_id (with stage names and probabilities aligned to the customer's pipeline). Podio deal amount maps to Odoo planned_revenue; deal name maps to name. Reference fields to Contact and Organization apps become Odoo Many2one fields (partner_id and partner_id.company_id). Close date maps to date_deadline.

Podio tasks that are standalone and not tied to a specific app map to project.task if the customer uses Odoo Project, or crm.activity if tasks should appear in the CRM pipeline activity view. Task title, due date, assignee, and completion status migrate directly. Linked item references from Podio (tasks linked to app items) become Many2one relations to the migrated record in Odoo.

Podio items are rows within an app and inherit the app's field schema. We migrate item values field-by-field, applying type conversions: Podio category fields become Odoo selection or many2one fields; Podio multi-value fields become Odoo one2many or many2many tags fields; Podio number fields map to Odoo float fields; Podio date fields map to Odoo date fields. Null values are preserved as null, not as placeholder strings. Reference field values are captured during export and remapped as Many2one IDs after the target record is inserted.

Podio reference fields create explicit links between items in different apps. During migration we capture all reference field values, insert the parent record, then insert the child record, and update the Odoo Many2one field with the resolved destination record ID. For circular reference chains (A references B, B references A), we use a two-pass import: insert all records with null relational fields, then run a second pass to populate the Many2one IDs from the inserted ID map.

Podio comments attached to items, tasks, files, and spaces migrate to Odoo mail.message records linked via mail.thread. The comment author, timestamp, and body text migrate directly. Rich-text formatting is simplified to plain text or basic HTML. mail_message records appear in the Odoo chatter on the parent record (crm.lead, res.partner, project.task).

Podio files are downloaded to staging storage via the Podio Files API, then uploaded to Odoo via the ir.attachment model using the XML-RPC write method. Files are attached to the migrated parent record using the res_model and res_id fields on ir.attachment. Podio's 100MB per-file limit is preserved; files over 100MB are flagged and either split or excluded with a data loss disclosure provided to the customer.

Podio status messages are lightweight social-style posts within a workspace or space. They have no direct Odoo equivalent. We treat them as Odoo notes (note.note) or as internal mail.message records on the workspace-equivalent record. The author, timestamp, and message body migrate; reactions and likes do not transfer.

Podio conversations are private multi-user message threads. We export the full thread as a formatted text transcript, save it as a PDF or text file, and attach it to the relevant workspace-equivalent record in Odoo using ir.attachment. Odoo does not have a native conversation thread model; the transcript preserves the content for audit purposes.

Podio tags applied to items, tasks, and other objects map to Odoo crm.tag (on crm.lead) or res.partner.category (on res.partner). Multi-value tags from Podio migrate to Odoo many2many tags fields. Tag color coding from Podio does not transfer as color but is stored as text in a tag description field. The customer selects the tag strategy during scoping.

Podio category fields (single-value or multi-value option fields within an app) map to Odoo selection fields (if the options are few and fixed) or to many2one relational fields pointing to a dedicated tag model. Option labels and color coding migrate as text; color preservation requires Odoo Studio or developer customization which is documented as a post-migration task.

Podio rating fields (star ratings on items) map to Odoo float or integer fields. The rating scale (1-5 stars, 1-10) is preserved. If Odoo uses a rating addon, ratings migrate as rating.rating records linked to the parent res.partner or crm.lead.

Globiflow is a third-party automation layer on Podio and is not accessible via the Podio API. We cannot export Globiflow workflows programmatically. During discovery we document every active Globiflow flow: trigger type, conditions, filter logic, and output actions. The customer receives a written Globiflow inventory with a functional specification for rebuilding each flow as an Odoo automated action, server action, or base.automation rule.