Moving off Podio does not have to mean exporting spreadsheets and rebuilding everything by hand.
InfoLobby imports directly from Podio over Podio's API. You connect your Podio account once, then pull apps in one at a time — fields, records, attachments, views, and comments come across, and the relationships between apps are preserved. No CSV exports. No manual field mapping.
This guide walks the full migration, in the order you should actually do it.
Quick Answer
To migrate from Podio to InfoLobby: generate a Podio API key, add it to InfoLobby as an OAuth2 integration, then use Import from Podio when creating a table. Import your apps in dependency order — the app that others link to first — so relationships have something to point at.
The whole thing runs over Podio's API, so there is no export/import shuffle and no re-typing data.
Who This Migration Is For
- Podio users who want their apps, items, and relationships in one place without rebuilding by hand
- Teams leaving Podio who need comments and attachments to come across, not just rows
- Anyone who has related Podio apps (Customers → Projects, Deals → Companies) and wants those links intact after the move
Who This Is Not For
- Anyone who relies heavily on Podio calculation fields — formulas do not translate and are skipped (rebuild them as InfoLobby fields after import).
- Apps built on multi-relationship fields (one field linking to many items). The importer stops rather than guess — you will need to split or drop that field in Podio first.
- Teams that only need a one-time flat data dump — a CSV export is simpler than connecting an API.
Being upfront: this preserves structure and links, but it is not a lossless clone. Calculations and unsupported field types are the two things to plan around.
Before You Start
Two things need to be in place:
- File storage on the target workspace. Attachments and comment images upload into your storage, so the workspace needs managed storage (included on paid plans) or your own S3/FTP connected. Without it, the import can't land files.
- A Podio account with admin access to the apps you want to bring over.
That's it. Now the steps.
Step 1: Create a Podio API Key
In Podio, go to your account settings, then the API keys tab (directly at podio.com/settings/api).
- Give the key a name —
InfoLobbyworks. - For the domain, enter
infolobby.com. - Click Generate API Key.
Podio shows you a Client ID and a Client Secret. Keep that tab open — you need both in the next step.
Step 2: Connect Podio to InfoLobby (OAuth2)
In InfoLobby, open the main menu and go to Integrations → Add Integration, and choose OAuth2 Service API. Podio is a standard OAuth2 provider, so this generic connector is all you need.
Fill in:
- Connection name —
Podio - Client ID — paste from Podio
- Client Secret — paste from Podio
- 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
These three URLs are also listed on the Import from Podio help page if you'd rather copy them from there.
Click Authenticate. A Podio window pops up — click Grant Access, wait for the success confirmation, then Save. Podio is now connected to your InfoLobby account.
Step 3: Import Apps in the Right Order
This is the one part that trips people up, so do it deliberately.
When you create a new table — from Add Table on an empty workspace, or from the table drop-down — you'll now see Import from Podio. Select it, then pick your organization → workspace → app.
Import the app that others depend on first. Relationships in Podio point at items in another app. If you import Projects before Customers, the customer links have nothing to attach to. So:
- Import Customers first (the app nothing else depends on).
- Then import Projects (which links to Customers).
- Continue outward — each app after the ones it references.
There's also a Follow imported records checkbox, off by default. Leave it off for large imports so you don't get a flood of follow notifications; turn it on if you want to subscribe to the new table and its records. You can follow or unfollow later either way.
Click Import and wait. A small app finishes in seconds; larger ones with attachments and comments take longer, and the progress bar tells you where it is.
Step 4: Map the Relationships
When you import an app that has a relationship field — say Projects linking to Customers — InfoLobby asks you to map it to a lookup field.
Because you already imported Customers, that table is right there in the dropdown. Pick it, and every project that was linked to a customer in Podio lands linked to the same customer in InfoLobby. If you don't want a particular link, choose Drop this lookup to skip it.
Behind the scenes, InfoLobby keeps each Podio item's original id on a hidden column and uses it to reconnect the links — which is exactly why import order matters. Items imported later can find the ones imported earlier; the reverse can't happen.
Repeat Steps 3 and 4 for each app until your workspace is complete.
What Comes Across — And What Doesn't
Set expectations before you start so nothing surprises you mid-migration.
| Podio | InfoLobby |
|---|---|
| App fields (text, number, money, date, category, location, embed, image, contact, phone, email) | Mapped to the closest equivalent field type |
| Single-relationship fields | Lookup fields — you pick the target table during import |
| Items | Records, with the original Podio item id preserved |
| Attachments + image fields | Files uploaded into your storage |
| Views (filters and sorts) | Grid views, best-effort filter translation |
| Comments | Comments, with original timestamps kept |
| Comment attachments + inline images | Files uploaded, markdown rewritten to point at them |
| Calculation fields | Skipped — rebuild as InfoLobby fields |
| Multi-relationship fields | Stops the import — split or remove first |
Comment authorship is matched to the closest workspace member: first by email, then by display name, and if neither matches, the comment is posted as System with an Originally posted by <name>: line so nothing is lost. Timestamps are always preserved verbatim.
Common Questions During Migration
"The import paused — is it stuck?" No. Podio rate-limits its API per user. When it hits a limit, InfoLobby waits and retries automatically, showing a paused message. Large migrations breathe like this; let it run.
"Do I have to move my whole workspace at once?" No. It's one app per import, on purpose. You can migrate a single app to try it, or work through an entire workspace app by app.
"Will my Podio data change?" No. The import only reads from Podio. Your Podio account is untouched, so you can migrate at your own pace and keep Podio live until you're confident.
"What about the formulas I had in Podio?" Calculation fields don't come across — formulas don't translate cleanly between platforms. Note which fields were calculated and rebuild them in InfoLobby afterward, where they'll recompute on your imported data.
FAQ
How do I migrate data from Podio to InfoLobby?
Generate a Podio API key, add it to InfoLobby as an OAuth2 integration, then choose Import from Podio when creating a table. Import apps in dependency order so relationships reconnect. Records, attachments, views, and comments come across over the API — no CSV exports.
Does the Podio import preserve relationships between apps?
Yes, as long as you import in the right order. Import the app that others link to first (for example Customers before Projects). InfoLobby maps each single-relationship field to a lookup and reconnects links using the preserved Podio item id.
Do I need to export CSVs from Podio?
No. The migration runs entirely through Podio's API using an OAuth2 connection, so there are no manual exports or field-by-field mapping.
What Podio data does not transfer?
Calculation fields are skipped (formulas don't translate) and multi-relationship fields stop the import until you split or remove them. Everything else — standard fields, items, attachments, views, and comments — is brought across.
Is my Podio account affected by the import?
No. The import only reads from Podio. Your Podio data stays exactly as it is, so you can keep both running until the migration is complete.
Can I migrate just one Podio app to test it first?
Yes. Import is one app at a time. Bring over a single app, confirm the fields and records look right, then work through the rest of your workspace.
Start Your Migration
Connect Podio once, then bring your apps across one at a time — with their records, files, comments, and links intact.
Read the full Import from Podio guide or start building your InfoLobby workspace.