Podium and Unthread share no structural overlap. Migration requires custom API-based ETL, conversation threading reconstruction, and an archival strategy for data with no Unthread equivalent.
There is no native migration path between Podium and Unthread, as the two platforms share almost no structural overlap — Podium is a customer interaction platform built around SMS, webchat, reviews, and payments for local businesses, while Unthread is a Slack-native AI helpdesk centered on ticket lifecycle management. The fundamental data model difference is that Podium is conversation-first and channel-agnostic, whereas Unthread is ticket-first and Slack-native, with entire categories of Podium data (reviews, payments, campaigns) having no Unthread equivalent. A custom API-based ETL pipeline or managed migration service is required, as CSV exports only cover contacts without conversation threading, and middleware tools cannot handle bulk historical migration at scale.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
Unthread's public API exposes emailDomains on Customers, not a direct phone field
Keep exact phone numbers in ticket fields, metadata, or your CRM if agents need them post-migration. (docs.unthread.io)
Unthread conversations are typed (slack, email, triage)
Historical Podium conversations without an active Slack channel should use triage. The Unthread public docs do not show timestamp override fields for imported conversations or messages, so exact historical chronology may require transcript-style preservation (e.g., prepending [2025-03-15 14:32 UTC] Agent Name: to each message body) rather than native backdating. (docs.unthread.io)
Unthread API constraints
All list endpoints cap at 100 records per page. File attachments are limited to 20MB per file and 10 files per Slack message. Unthread does not publish write endpoint rate limits in its public docs — start at ~1 request/second and increase gradually, monitoring for 429 responses. Based on migration experience, Unthread's API sustains ~60–90 write operations/minute without throttling. Plan your validation queries and attachment splitting accordingly. (docs.unthread.io)
The runbook
Work top to bottom. Tick steps as you go — your progress is saved in this browser.
01 Discovery Establish why you are moving, what "done" means, and who signs off.
Objective A written scope with agreed success criteria, a named owner per workstream, and a budget approved by finance.
Keep these open
-
Pull the real numbers out of Podium
Export counts for tickets (open and closed separately), contacts, organisations, attachments, macros, triggers, automations, views and SLA policies. Note the oldest ticket date — history depth drives the whole timeline. Estimating from memory is the single most common cause of a blown migration window.
Data Profiler Get real record counts instead of estimating from memory -
Decide what history actually moves
Agree a cut-off with the support lead: all history, last 24 months, or open tickets plus a read-only archive. Every extra year of closed tickets adds API time and cost without adding much agent value. Get this in writing — it is the decision people relitigate mid-cutover.
A "move everything" default is what turns a two-week migration into a two-month one.
COI & ROI Calculator Build the 36-month business case you will need for sign-off -
Confirm Unthread can hold your support model
Walk your current workflow through Unthread: multi-brand, business hours, SLA targets, CSAT, side conversations, public vs internal notes, and any channel you depend on (voice, chat, WhatsApp, social). List anything with no native equivalent — those are project risks, not configuration details.
-
Build the business case
Model licence delta, migration effort, agent retraining, and the cost of staying put (Cost of Inaction). Executives approve a number, not a plan, and you will be asked for it again at the go/no-go.
Helpdesk Migration Planner Turn ticket volume into a dated Podium → Unthread timeline -
Name owners and set the go/no-go date
One named owner each for data, configuration, integrations, and agent enablement, plus a decision-maker who can call a rollback. Put the go/no-go meeting in calendars now, 48 hours before the freeze.
Podium → Unthread specifics
- Channel realignment
- Podium is built for external-facing SMS, webchat, and review management for local businesses. Teams whose support operations have shifted to Slack-based B2B customer communication or internal IT/HR support need a platform built for that workflow. Among Slack-native helpdesks (Halp, Thena, Foqal, ClearFeed), Unthread differentiates by offering full ticket lifecycle management with SLAs, AI agents, and native email/in-app chat channels — making it suitable as a primary helpdesk rather than a Slack add-on.
- Operational maturity
- Podium has no concept of SLAs, ticket types, escalation paths, or structured routing. When support operations grow beyond "reply to texts" into tracked, prioritized ticket management, Unthread is purpose-built for that.
- AI-native support
- Unthread's AI agents operate directly inside Slack channels for auto-classification, suggested responses, and ticket resolution. Podium's AI features are add-ons focused on review responses and receptionist functionality, not ticket resolution.
- Cost structure
- Podium's published plans start at $399/month (Core) and scale to $599+/month (Pro) with per-location fees and add-ons. Unthread starts at $50/agent/month (Basic) or $75/agent/month (Pro). For a 5-agent team, that's $250–$375/month on Unthread vs. $399–$599+/month on Podium — a 35–60% reduction for teams that primarily need ticketing and conversation tracking. Verify current pricing directly with each vendor before planning, as both have changed pricing in the past 12 months.
- Ongoing sync during transition
- Middleware bridge for net-new data + API migration for historical data
Don't move on until
- Record counts confirmed for tickets, contacts, organisations and macros
- Success criteria signed off by the support lead
- Freeze window provisionally booked with the business
02 Data Audit Find out what is actually in the data before you try to move it.
Objective A profiled, cleaned export with every quality defect either fixed at source or explicitly accepted.
Keep these open
-
Take a full Podium export and profile it
Export to CSV or JSON and profile every file: row counts, null rates per column, distinct values, and type consistency. Compare row counts against the API totals from Discovery — a gap here means your export is silently truncated, usually by pagination.
Data Profiler Profile the Podium export for nulls, outliers and type drift -
Validate file structure before anyone writes a transform
Check delimiters, quoting, encoding (expect UTF-8, watch for BOMs and Latin-1), duplicate headers, and embedded newlines in ticket bodies. Ticket descriptions with raw newlines and commas break naive CSV parsers and silently shift columns.
A single unescaped quote in one ticket body can shift every subsequent column without any error.
CSV Validator Catch broken headers and ragged rows in the raw export -
Inventory PII and set retention
Scan for emails, phone numbers, payment card fragments, national IDs and anything else regulated in ticket bodies and custom fields — support tickets are where customers paste things they should not. Decide what gets migrated, masked, or dropped, and record the legal basis.
Ticket bodies and attachments routinely contain card and ID data that never appears in a structured field.
PII & Compliance Scanner Find regulated fields before they land in a new system -
Quantify duplicates, orphans and dead references
Count duplicate contacts (same email, different casing), tickets whose requester no longer exists, organisations with no members, and attachments whose parent ticket is gone. Fix these in Podium where you can — migrating them just moves the mess.
Data Cleaner Strip empty rows, stray whitespace and dead columns -
Clean and normalise the export
Trim whitespace, drop empty rows and columns, normalise casing on emails and tags, and standardise every timestamp to UTC ISO 8601. Timezone drift is invisible at load time and shows up weeks later as SLA reports nobody can reconcile.
-
Produce a masked copy for sandbox work
Generate a realistic but fake version of the export for testing and for any vendor who needs sample data. Loading real customer PII into a sandbox is a breach in most jurisdictions, and sandboxes are rarely covered by your DPA.
PII Masker Generate a safe copy for sandbox and vendor testing
Don't move on until
- Export parses cleanly with no ragged rows or encoding errors
- PII inventory complete and retention decisions recorded
- Duplicate and orphan records quantified and triaged
03 Field Mapping Turn two schemas into one signed-off mapping spec.
Objective A reviewed field-level mapping covering every object, with an explicit decision for every field that has no target.
Keep these open
-
Generate the first-pass Podium → Unthread field map
Start from an automated match on both schemas, then review every row by hand. Automated matching gets the obvious 70% right and is confidently wrong on the rest — especially anything named "type", "status" or "custom_field_1".
Schema Mapper Opens pre-loaded with the Podium → Unthread field pair -
Map status, priority and channel values, not just field names
Enumerate every value in each picklist on both sides and map them explicitly. Value-level mismatches are the defect class that survives all the way to production because the field itself mapped fine — a ticket that should be "Pending" arriving as "Open" reopens SLA clocks.
Statuses with no target equivalent (on-hold, pending-customer) need a policy decision, not a best guess.
-
Decide how custom fields land
Create the target custom fields first, matching type exactly (a dropdown mapped to free text can never be mapped back). Where Unthread has no equivalent, decide between a new custom field, a tag, or a note appended to the ticket body — and record which.
-
Resolve identity and threading
Decide how source IDs are preserved — most platforms will not let you set the primary key, so keep the original ID in a custom field. Without it, reconciliation becomes fuzzy matching and every future support question about an old ticket is unanswerable.
Losing the original ticket ID makes reconciliation and rollback effectively impossible.
-
Plan attachments, inline images and threading order
Confirm size limits, allowed MIME types, and whether inline images survive as attachments or need rehosting. Decide the comment ordering and author attribution rules: comments loaded out of order, or all attributed to the API user, destroy the conversation history agents rely on.
-
Freeze and sign off the mapping spec
Version the spec, walk the support lead through it row by row, and get explicit sign-off. Any change after this point goes through change control — mid-flight mapping edits are how partial loads happen.
-
Deduplicate contacts
by contact_uid — Podium contacts can have multiple channel entries (phone, email, secure) for the same person. Without deduplication, you'll create 2–3x the expected Customer/Account count.
-
Map statuses
from Podium's binary open/closed to Unthread's four-state model (open, in_progress, on_hold, closed).
-
Generate placeholder emails
for SMS-only contacts to satisfy Unthread's schema requirements (e.g., {phone}@podium-archive.local).
Podium → Unthread specifics
- Reconstruct conversation threads
- by grouping conversation_item rows by conversation_uid, ordered by conversation_item_inserted_at.
- Strip or convert message formatting
- Podium messages are plain text; Unthread expects Slack-compatible markdown (mrkdwn). Convert any HTML entities, strip unsupported formatting.
Don't move on until
- Every source field is mapped, deliberately dropped, or parked in a custom field
- Status, priority and channel value maps agreed with the support lead
- Mapping spec version-controlled and signed off
04 Test Migration Prove the pipeline on a small, representative slice.
Objective A pilot load into a Unthread sandbox that reconciles cleanly and has been reviewed by real agents.
Keep these open
-
Stand up a Unthread sandbox that matches production config
Create the custom fields, groups, brands, business hours and SLA policies first. A pilot into a default sandbox tests nothing, because the failures you care about are all configuration mismatches.
-
Pick a deliberately nasty pilot sample
Take 500-1000 records chosen for difficulty, not convenience: the longest ticket threads, tickets with the most attachments, non-Latin character sets, merged and split tickets, deleted requesters, and every status value. A clean random sample proves only that easy records are easy.
-
Run the load with masked data and instrument everything
Log every API request and response with its source record ID. When 40 records fail out of 10,000 you need to know exactly which ones and why, without re-running the whole batch.
PII Masker Never load real customer PII into a sandbox -
Measure real throughput against the rate limit
Record achieved records-per-hour under Unthread's actual rate limits, including retries and backoff. Extrapolate to the full volume: if the maths says the full load exceeds your freeze window, you fix that now, not on cutover night.
Published rate limits are ceilings, not throughput. Assume real-world rates are meaningfully lower once retries and backoff are counted.
-
Reconcile the pilot and triage every failure
Diff source against target on record counts and field-level values. Every discrepancy gets a root cause and a fix — "probably fine" at pilot scale becomes thousands of broken records at full scale.
Migration Validation Tool Diff the pilot batch against source before scaling up -
Put real agents in front of the pilot data
Have two or three agents work sample tickets end to end in the sandbox. They find the things reconciliation cannot see: unreadable threading, missing context, macros that no longer make sense. Fix the mapping, then re-run.
Don't move on until
- Pilot batch reconciles to 100% on record counts
- Agents have reviewed sample tickets and confirmed they are workable
- Measured throughput extrapolates to a viable full-load window
05 Cutover Execute the switch inside a controlled, reversible window.
Objective All in-scope data live in Unthread, agents working in the new system, and a rollback path that stayed available throughout.
Keep these open
-
Pre-load history before the freeze
Load closed tickets and contacts days or weeks ahead while Podium stays live. Only open tickets and the final delta need to move inside the freeze — this is the single biggest lever on window length.
Helpdesk Migration Planner Size the freeze window from Unthread's real API limits -
Publish the runbook with times, owners and abort criteria
A timed sequence: freeze start, final export, delta load, channel switch, smoke test, go/no-go, agent switch. Name who does each step and the explicit condition that triggers a rollback. Decide the abort criteria before the night, when nobody wants to be the one to call it.
-
Freeze Podium and take the final delta
Stop new ticket creation, let agents finish in-flight replies, then export everything changed since the pre-load. Announce the freeze to the whole business, not just support — someone always tries to raise a ticket during it.
Tickets created during an unenforced freeze land in the old system and are the most common source of permanently lost data.
-
Load the delta and open tickets
Run the delta load, then reconcile counts before touching any channel. Do not repoint email until the delta has verified — an inbound ticket arriving mid-load is far harder to untangle than a few extra minutes of freeze.
Migration Validation Tool Confirm the final delta landed before you reopen -
Repoint channels and verify with live traffic
Switch email forwarding and MX or connector settings, update chat widgets and web forms, and re-authorise integrations. Then send real test tickets through every channel and confirm each lands, routes and triggers the right automation.
Email forwarding changes can take up to a full DNS TTL to propagate — check the TTL days in advance and lower it if needed.
Cron Expression Builder Schedule the delta syncs that run through the freeze -
Run the go/no-go and switch the agents
Walk the exit criteria with the decision-maker, call it explicitly, then move agents over with a named person on hand for the first few hours. Keep Podium read-only rather than cancelled — cancelling the old contract on day one removes your only fallback.
Don't move on until
- Full historical load complete and counts matched
- Inbound channels repointed and verified with live test tickets
- Rollback decision point passed explicitly, not by default
06 Validation Prove the migration is complete, then close it out.
Objective Documented evidence that data, workflow and reporting all survived, and a signed acceptance.
Keep these open
-
Run the full reconciliation
Compare source and target on every object: total counts, counts by status, counts by group, attachment counts, and field-level spot checks on a random sample. Produce one report you can hand to an auditor.
Migration Validation Tool Reconcile Podium and Unthread record-for-record -
Verify field completeness, not just record counts
Re-profile the loaded data and compare null rates per field against the source profile. Matching record counts with a field that silently arrived empty is the failure mode counts alone will never catch.
Data Profiler Prove field completeness held up through the load -
Rebuild reporting and compare against baselines
Recreate your core dashboards — volume, first response time, resolution time, CSAT — and compare to pre-migration figures for the same period. Explain every variance; a changed SLA calculation is a real finding, not a rounding error.
SLA and first-response metrics are usually recalculated from the loaded timestamps, so they will differ if any timestamp mapping was approximate.
-
Test the workflow layer end to end
Fire every trigger, automation, SLA escalation, macro and notification with a live ticket. Workflow does not migrate — it gets rebuilt — so it is untested until someone has actually watched it run.
-
Confirm compliance and produce the audit trail
Re-scan the loaded data for regulated fields, confirm retention and deletion policies are configured in Unthread, and file the evidence with your PII decisions from the audit phase.
PII & Compliance Scanner Produce the compliance evidence your auditor will ask for -
Sign off, then decommission on a schedule
Get written acceptance against the Discovery success criteria. Keep Podium read-only for an agreed period (30-90 days is typical), take a final archive export, and only then cancel. Diarise the decommission date so it does not quietly renew.
Don't move on until
- Full reconciliation report attached to the project record
- Reporting baselines match pre-migration figures within agreed tolerance
- Formal acceptance signed and archive retention scheduled
Field mapping reference
The field-by-field mapping for each object. Use this as the starting point for your mapping spec.
Data Category Podium Source
| Podium field | Unthread field | Notes |
|---|---|---|
| Contacts | Contacts table | Map to Unthread Customers or Accounts |
| Conversations | Messages table | Decide on date cutoff — migrate last 12–24 months |
| Message History | Messages table (conversation_item_body) | Reconstruct threads from conversation_uid |
| Locations | Location and Organizations table | Map to Unthread Accounts or Tags |
| Reviews | Reviews + Review Invites tables | No Unthread equivalent |
| Payments | Payments table | No Unthread equivalent |
| Campaigns | Campaigns + Campaign Contacts tables | Unthread outbound is Slack-only |
| Feedback/Surveys | Feedback table | No Unthread equivalent |
| Custom Fields | Contact custom fields (up to 8) | Map to Unthread Ticket Type Fields |
| Attachments | Via API (expiring URLs) | Download immediately — URLs expire after 7 days (docs.podium.com) |
Conversations Conversations
Podium's continuous conversation model must be translated into Unthread's discrete ticket model, requiring complex thread reconstruction from flat message rows and deliberate schema translation.
| Podium field | Unthread field | Notes |
|---|---|---|
| conversation_uid | metadata.podium_conv_uid | Store for traceability |
| conversation_inserted_at | createdAt | ISO 8601 format |
| conversation_is_closed | status | true → closed, false → open |
| conversation_assigned_user_uid | assignedToUserId | Map to Unthread user ID |
| inbox_name | ticketTypeId | Map inbox to Ticket Type |
| conversation_channel_type | type | Map to email or triage |
| First conversation_item_body | markdown (initial message) | Plain text or Slack-compatible markdown |
Messages Messages
| Podium field | Unthread field | Notes |
|---|---|---|
| conversation_item_body | markdown | Text content of the message |
| conversation_item_inserted_at | Chronological ordering | Unthread auto-timestamps; original timestamp should be embedded in message body |
| conversation_item_sender_name | onBehalfOf.name | For email-type conversations |
| conversation_item_type | isPrivateNote | Internal notes → true |
| Attachment content type | Attachment via multipart form | 20MB max per file, 10 files per message |
Cus m Fields
Contacts are available via CSV export and API with core fields (name, phone, email, tags), making extraction straightforward though deduplication across channel types is needed.
| Podium field | Unthread field | Notes |
|---|---|---|
| STRING | short-answer | Direct |
| BOOLEAN | checkbox | Direct |
| DATETIME | date | Strip time component if Unthread date field is date-only |
| FLOAT, INTEGER | short-answer | Convert to string; Unthread has no numeric field type |
| SINGLE_SELECT | single-select | Normalize picklist values before loading |
| MULTI_SELECT | multi-select | Normalize picklist values before loading |
Podium Unthread
| Podium field | Unthread field | Notes |
|---|---|---|
| contact_uid | customFields [podium_id] | String, for traceability |
| contact_name | name | Direct map |
| channel_unique_identifier (email) | emailsAndDomains [] | Array |
| contact.phoneNumber | customFields [podium_phone] | No first-class phone field in Unthread customer docs |
| contact_opt_in_tags | name | Create via POST /tags, then link |
| location_name | name | Direct map |
| organization_name | customFields [org] | String |
| conversation_uid | metadata.podium_conv_uid | For traceability |
| conversation_inserted_at | Embedded in markdown body | No timestamp override available |
| conversation_is_closed | status | true → closed |
| conversation_item_body | markdown | Text content; set isPrivateNote: true for closed conversations |
| conversation_item_sender_name | onBehalfOf.name | For email-type conversations |
| conversation_assigned_user_uid | assignedToUserId | Map to Unthread user ID; use fallback for departed agents |
| inbox_name | ticketTypeId | Map to Ticket Type via crosswalk |
| conversation_first_webchat_url | metadata.source_url | Preserve in metadata |
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Contacts / Customers | low | Contacts are available via CSV export and API with core fields (name, phone, email, tags), making extraction straightforward though deduplication across channel types is needed. |
| Conversations / Tickets | high | Podium's continuous conversation model must be translated into Unthread's discrete ticket model, requiring complex thread reconstruction from flat message rows and deliberate schema translation. |
| Message History | high | Full message extraction requires API-based migration with rate limit constraints, and preserving sender attribution, chronological order, and threading across SMS/webchat/email channels adds significant complexity. |
| Tags | low | Both platforms support tags on contacts/customers and conversations, making this a relatively direct mapping with minimal transformation required. |
| Custom Fields | medium | Podium supports up to 8 contact custom fields that must be mapped to Unthread's Ticket Type Fields, which have different supported types (short-answer, multi-select, checkbox, user-select) requiring type conversion logic. |
| Attachments | high | Binary file attachments are excluded from Podium's FTP exports and must be extracted separately via the API, then re-uploaded to Unthread with correct message association. |
| Reviews | medium | Unthread has no equivalent for review invites, ratings, or review bodies, so this data must be archived externally before migration to avoid permanent loss. |
| Payments / Invoices | medium | Payment and invoice records have no Unthread equivalent and must be exported and archived separately, with risk of data loss if not handled before cutover. |
| Campaigns | medium | Campaign messages, interactions, and opt-in/opt-out records have no Unthread counterpart since Unthread's outbound is Slack-only, requiring archival before migration. |
| Organization / Location Hierarchy | medium | Podium's multi-level Organization→Location hierarchy must be flattened into Unthread's single-level Account model, potentially losing hierarchical relationships. |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
Conversation Thread Reconstruction
Podium's flat message rows keyed by conversation_uid must be reassembled into threaded Unthread conversations with correct chronological ordering, sender attribution, and status mapping.
Contact Deduplication Across Channels
The same person can have multiple Podium contact channel entries across phone, email, and secure channels, all of which must be merged into a single Unthread Customer record.
No Equivalent for Reviews/Payments/Campaigns
Podium's reviews, payment records, and campaign data have no native Unthread equivalent and must be archived or discarded before migration.
API Rate Limit Constraints
Podium throttles sustained extraction above ~2 requests/second and Unthread's write rate limits are undocumented, making extraction of 10K+ conversations potentially take 2–4 days of continuous API calls.
Status Model Mismatch
Podium uses a binary Open/Closed status model that must be mapped to Unthread's four-state model (Open, In Progress, On Hold, Closed), requiring business rules to determine intermediate states.
Attachment Handling Gap
Message attachments are excluded from Podium's FTP exports and require separate API-based extraction and re-upload into Unthread's system.
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
Can I migrate Podium conversation history to Unthread with CSV alone?
No. Podium's native CSV export covers contacts only — Name, Phone, Email, Contact Status, Address, Tags, and Date Added. Full conversation history, messages, and attachments require API-based extraction or Podium's FTP raw data export combined with Unthread API ingestion.
What Podium data cannot be migrated to Unthread?
Reviews, review invites, payment/invoice records, campaign data, and feedback surveys have no Unthread equivalent. These should be archived separately before migration. Podium's lead-specific analytics fields (first response time, conversion time) also have no mapping in Unthread.
How long does a Podium to Unthread migration take?
For small datasets under 5K conversations, expect 1–2 weeks including planning, scripting, and validation. For mid-size datasets (10K–50K conversations), budget 2–4 weeks with a dedicated developer. Podium's API rate limits are the primary bottleneck for API-based extraction.
Will historical Podium messages show up in Slack via Unthread?
No. Historical messages imported via API are accessible and searchable within the Unthread web dashboard, but they cannot be retroactively injected into Slack channels. Unthread's Slack backfill only covers 6 months of Slack-native messages.
Can I run Podium and Unthread in parallel during cutover?
Yes. The common pattern is to complete the historical backfill first via API or FTP, then run a short webhook-based delta sync to capture new records in Podium until you finalize the cutover to Unthread.