Migrate from Podio to Freshsales

We inspect each Podio app's field schema during discovery. Apps with contact-like fields (name, email, phone, organization) map to Freshsales Contact. Apps representing organizations or companies map to Freshsales Account. Apps tracking sales opportunities map to Freshsales Deal. The mapping is per-app, not per-workspace — a single Podio workspace may contain apps that map to multiple Freshsales objects. We document this per-app classification in the discovery report before any data moves.

Podio workspaces often contain apps used to track meetings, calls, or follow-ups. We map these to Freshsales Tasks with status, priority, due date, and assignees preserved. Comment fields on activity apps migrate as Freshsales Notes attached to the parent record. Activity timestamps are preserved in the ActivityDate field.

Podio items are rows within an app. Each item's field values map to the corresponding Freshsales field based on the parent app's classification. Multi-value category fields (Podio categories with multiple selections) map to Freshsales multi-select picklist. Date fields map to Freshsales date fields with format normalization. Null values are preserved as null rather than defaulting to placeholder text.

Podio reference fields create explicit links between items in different apps, functioning like foreign keys. Freshsales does not have a cross-object reference field equivalent for all record types. We capture all reference field values during export, then write them as formatted notes on the target record (e.g., 'Originally linked to: [Item Name] in Podio app [App Name]') or as text fields if the destination has a matching record type. We flag reference chains longer than two hops for manual review.

Podio standalone tasks map directly to Freshsales Tasks with title, due date, assignee (resolved by email to Freshsales User), completion status, and linked item reference preserved. Recurring task rules are documented for manual rebuild in Freshsales Workflows. Tasks linked to specific items carry the parent app's mapping forward so the relationship context is retained.

Comments on Podio items, tasks, and files migrate as Freshsales Notes attached to the relevant record. Rich-text formatting simplifies to plain text. The comment author and timestamp are preserved in the Note body header. Comments on objects that do not map to a Freshsales equivalent are attached to the nearest parent record and flagged in the reconciliation report.

Podio files attach to items, tasks, and spaces via the Files API (separate from Items API). We download files to staging storage, then re-upload to Freshsales if the record type supports attachments. Files above 25 MB or unsupported file types are flagged and replaced with a note containing the original filename and a link to the Podio download URL for manual retrieval.

Podio tags on items migrate to Freshsales custom multi-select picklist fields on the target object. We flatten multi-value tag sets into a single picklist field if the tag count stays below Freshsales' 500-option limit. Tags used for categorization are distinguished from labels during discovery so that classification tags map correctly.

Podio category fields (single-value or multi-value option sets within an app) map directly to Freshsales picklist or multi-select picklist fields. Option labels and color coding from Podio transfer as text labels; color metadata is noted but not natively supported in Freshsales. We validate that option values do not exceed Freshsales' 500-option maximum per field.

Podio workspaces are top-level organizational containers with member lists and permissions. Freshsales has no workspace concept. We capture the workspace name on each record as a custom text field (podio_workspace__c) so that teams can filter reports by the original workspace without rebuilding the organizational boundary. Workspace-level permissions do not migrate and require Freshsales profile and permission set configuration post-migration.