Migrate from Podio to Microsoft Dynamics 365 Sales

Podio's top-level org hierarchy (Org > Workspace > Space > App > Item) does not map directly to a single Dynamics 365 entity. We map each Podio workspace to either a Business Unit or a Team in Microsoft Dynamics 365 Sales , depending on whether the destination uses Business Unit isolation for data access control. Workspace member lists map to Team Membership. Org-level settings are documented as a configuration handoff rather than migrated data.

Podio Spaces sit inside workspaces as sub-containers. We map them to Dynamics 365 Teams with member lists preserved, or to a custom Dataverse entity (e.g., BusinessUnit or Division) if the customer requires hierarchical reporting at the space level. Space-level permissions map to Team security roles.

Each Podio app is a user-built table with a unique field schema. We reverse-engineer the app's field structure during discovery and map it to a custom Dataverse entity in Dynamics 365. Standard Podio field types (text, number, date, category, link, relationship) map to their Dataverse column type equivalents. Reference fields within the app map to Dataverse lookup columns pointing to related custom entities. Apps with no clear CRM equivalent (e.g., inventory trackers, issue logs) become custom entities with a scope disclosure for fields that cannot map cleanly.

Podio Contacts are user profiles with name, email, title, and organization fields stored in a contact-type app. We map these to Dynamics 365 Contact records, using email address as the deduplication key. Custom contact fields in the Podio app migrate to custom columns on the Contact entity. If the source Podio workspace uses a separate Contact app for clients, those records also map to Contact rather than Account unless they represent organizations.

If the Podio workspace includes an app tracking organizations (with company name, domain, address, industry), we map it to Dynamics 365 Account. The organization's primary contact in Podio maps to the Account's Primary Contact lookup. Company-level custom fields migrate as custom columns on Account.

Podio apps used to track sales pipeline (deal name, value, stage, close date, owner) map to Dynamics 365 Opportunity. The Podio app's stage field maps to a Sales Process stage in Dynamics 365. If the customer uses multiple Podio apps to track different product lines, each maps to a separate Opportunity Record Type. Deal owner maps to Opportunity OwnerId resolved by email match against the User table.

Podio Tasks migrate to Dynamics 365 Task records linked to the parent Contact, Account, or Opportunity via the WhatId field. We preserve task title, due date, completion status, and assignee. Recurring task rules are documented separately because they require manual rebuild in Power Automate. Item-linked tasks in Podio resolve to the corresponding migrated entity record in Dynamics 365.

Podio Comments attached to items migrate as Annotation records linked via the objectid and objecttypecode fields to the target Contact, Account, Opportunity, or custom entity. Comment author and timestamp migrate. Rich-text formatting is simplified to plain text. If the destination entity does not support annotations directly, comments attach as Note records.

Podio file attachments use the Files API, which is separate from the Items API. We download each file to our staging storage, then re-upload to Dynamics 365 as an Annotation (Note) attached to the parent record, or to SharePoint document management if the destination org uses SharePoint integration. Filename, upload date, and uploader migrate. Podio's 100MB per-file limit applies on the source side.

Podio status messages are lightweight social-style posts within a space or workspace. We treat them as Annotation records attached to the relevant workspace-equivalent entity (e.g., Account or a custom Division entity). They do not have a native equivalent in Microsoft Dynamics 365 Sales . We flag this as a scope disclosure item: status messages migrate as a flat text feed but lose their social-post context.