Move your data from Podio

InfoLobby reads your Podio data through your own Podio API key so you can move it here. There are three ways in, depending on how much you're bringing:

All three read only the workspaces you select, using the credentials you supply.

Prerequisites

1. Add a Podio OAuth2 integration on the integrations page:
   • Authorize URL: https://podio.com/oauth/authorize
   • Access Token URL: https://podio.com/oauth/token
   • Resource Owner Details URL: https://api.podio.com/user/status
   • Client ID / Client Secret: register a Podio API client at podio.com/settings/api and paste them here
2. Click Authenticate on the integration and complete the Podio login.
3. The target workspace must already have file storage configured (managed or BYO S3/FTP) — attachments and comment files require it.

Once the integration is saved, a Podio Tools row appears on it with the Migrate from Podio and Plan my Podio migration buttons, and the workspace overview's Add Table dialog gains an Import from Podio option.

Migration plan

A read-only report on the workspaces you pick — nothing is created or changed. Use it to see the shape of the move before you commit to it.

Pick an organisation, tick the workspaces, and InfoLobby reads their structure: apps, record counts, fields, relationships and automations. You get a report you can read in the browser or download as a PDF, covering:

• Every app, its fields and its record count
• Relationships between apps, including a diagram, and which ones point at apps you didn't select
• Calculation fields and how convertible they look
• Anything that can't be imported as-is, with the reason
• Your GlobiFlow automations and how each one would translate (see below), if you connect the cookie

Schema, counts and automation summaries are read to build the plan — no item data is exported, and the report is yours alone.

Migrate from Podio

The full move. Each Podio workspace you select becomes an InfoLobby workspace, and every app you tick becomes a table inside it.

The wizard runs in two stages:

1. Analyze — read-only. Pick the organisation, workspaces and apps, then InfoLobby profiles them and shows you what will happen: which apps import cleanly, which are blocked and why, and any relationships pointing at apps outside your selection. Abandoning the wizard here leaves nothing behind.
2. Create — the only step with side effects. Choose a new or existing InfoLobby workspace for each Podio workspace, resolve any out-of-batch relationships, then run it.

What multi-app migration solves

A single-app import can't represent a relationship to an app it isn't importing. The migrator handles the whole batch at once, so cross-app, self-referencing and mutual/circular relationships all resolve — tables are created first, rows imported, then relationships wired up and foreign keys added last.

Relationships pointing at an app outside your selection are listed during the wizard, and you map each one to an existing table or drop it. The target table can live in another workspace as long as it's on the same database.

GlobiFlow automations

If you use GlobiFlow, both the migration plan and the migrator can include your automations. GlobiFlow has no OAuth, so you paste its xpodioflow cookie into the wizard — there's a How do I get this? link with the steps. The cookie is tested before the wizard continues; leave it blank to skip automations entirely.

Automations are migrated after your tables exist, so triggers and cross-app actions can resolve to real tables and columns. Each flow gets one of three verdicts:

• Auto — translates cleanly
• Needs review — translates, but something needs your attention (a webhook endpoint, an unmapped reference)
• Unsupported — can't be translated; listed with the reason

Imported automations arrive switched off. Review them, then activate — nothing goes live against your data without you turning it on. Flows whose Podio app wasn't part of the migration are summarised as a single line rather than listed individually.

The final report includes an Automations section listing what was created and a Flows needing attention list.

Import from Podio (single app)

The original single-app path, in the workspace overview's Add Table dialog. One Podio app becomes one new table. To pull in a related app, import that one first and then map the relationship back to it.

Use Migrate from Podio instead if you're bringing more than one app — it handles the relationships between them for you.

What gets imported

Following imported records

The wizard has a Follow imported records checkbox, which is off by default. Leave it off and you won't be subscribed to the new tables or the records they create — handy for large migrations where you don't want a flood of follow notifications. Turn it on to follow everything imported, just as if you'd created it by hand. You can always follow or unfollow a table or individual record later.

How comment authors are resolved

For each Podio comment, InfoLobby tries to attribute it to the closest workspace member:

1. Match the Podio user's email to a workspace member.
2. If no email match, match their display name to a workspace member's display name.
3. Otherwise post as System with a leading Originally posted by <name>: line.

Created-at timestamps are always preserved verbatim from Podio.

Running it again

Re-running over an app is a sync, not a duplicate. The hidden podio_id column matches each Podio item to the record it created, so:

• Existing records are updated (and the change shows in history)
• New Podio items are inserted
• Records whose Podio item no longer exists are removed — Podio stays the source of truth

Records you added by hand in InfoLobby have no podio_id and are never touched.

A migration that's interrupted can be resumed — progress is written durably as it goes, so a fresh run picks up where it stopped rather than starting over or duplicating work.

Rate limits

Podio's API has per-user rate limits. Imports handle 420/429 responses automatically by waiting and retrying, and you'll see progress messages while paused. Large organisations take a while — each item with attachments and comments is several Podio API calls.

Troubleshooting

• "No Podio integration is connected" — Add and authorize a Podio OAuth2 integration first.
• "Failed Refreshing expired Token" — Click Authenticate again on the Podio integration, complete Podio login, then save the integration.
• "Target workspace has no file storage configured" — Connect S3, FTP, or use the managed storage included with paid plans.
• "Field X is a Podio multi-relationship — import not supported" — Remove the field from the Podio app or split it before importing.
• A relationship couldn't be mapped — The wizard blocks until every required out-of-batch relationship points at a table or is dropped. Either include the target app in the migration or pick an existing table for it.
• Automations didn't come across — Check the GlobiFlow cookie was accepted (a dead cookie blocks the wizard with an inline error). Flows whose Podio app wasn't part of the migration are skipped by design.
• Imported automations aren't running — They're imported switched off on purpose. Review and activate them.
• Migration is slow — Progress messages name each app as it's processed, so you can see where it is.