Migrate from Podio to Nutshell

Podio apps configured as contact registries map to Nutshell Person records. We extract name, email, phone, title, and organization fields from the Podio app schema and map them to Nutshell's name, emails, phones, and title fields. Custom fields on the Podio contact app map to Nutshell custom fields on Person. Any Podio app with fewer than four person-identifying fields undergoes a naming audit during scoping to confirm it is a contact app and not a project or inventory app.

Podio apps storing business entities map to Nutshell Company records. The company name, website, address, and industry fields map to their Nutshell equivalents. A Podio organization app is distinguished from a contact app during discovery by the presence of a company domain field or business address field without a personal name field.

Podio's reference field lets a contact app item reference an organization app item, creating a Contact-to-Account relationship. We resolve this reference during migration by creating the Company record first, then creating the Person record with a nut_company_id link. If the Podio contact app does not use an explicit reference field and stores organization name as a text field, we attempt a fuzzy match on company name or create a new Company record as needed.

Podio apps tracking sales opportunities map to Nutshell Deal records. We identify deal apps during discovery by the presence of a monetary amount field, a stage or status category field, and an expected close date field. The Podio category values map to Nutshell Deal stages, which we configure as a pipeline in Nutshell before import. Owner assignment migrates via email-to-user lookup.

Podio task objects and apps with task-like schemas (title, due date, assignee, status) map to Nutshell Task records. We preserve task titles, due dates, completion status, and assignee assignment by resolving the assignee's email to a Nutshell user. Recurring task rules are not migratable and are flagged for the customer's admin to rebuild as Nutshell sales automation rules.

Podio comments on items, tasks, and files map to Nutshell Note records attached to the parent Person, Company, or Deal. Comment text, author name, and timestamp migrate. Rich-text formatting simplifies to plain text or basic markdown. If the destination Person, Company, or Deal has not yet been created at the time of comment migration (due to record-dependency ordering), we stage comments in a temporary lookup table and attach them after the parent record is confirmed.

Podio files attach via a separate Files API path from the Items API. We download each file to our staging storage, re-upload to Nutshell using its attachment API, and link the file to the correct parent record. Podio's 100MB per-file limit is honored; files exceeding this limit are flagged for manual delivery. Filenames and original attach dates are preserved in Nutshell's file metadata.

Podio status messages (lightweight social-style posts within a space) have no direct Nutshell equivalent. We export them as timestamped Note records attached to the nearest Nutshell object, or as a formatted activity log file if no parent record exists. The customer chooses during scoping whether to migrate status messages as notes or to exclude them to reduce noise in the target CRM.

Podio category fields (single-value or multi-value option fields) map to Nutshell custom dropdown or multi-select fields. We preserve option labels exactly. Podio color coding on categories does not transfer; we note the color assignments as a text annotation in the migration report for the customer to reapply manually in Nutshell if needed.

Podio tags applied to items map to a Nutshell custom multi-select field or a tag-style label on the record. We flatten multi-value tags into a single delimited string if the destination field does not support multi-select. The customer selects the tagging strategy during scoping.