Podium to Crisp migration requires a custom API-based ETL pipeline. CSV handles contacts only; conversations need the Crisp REST API with no native Podium adapter available. Plan for data model transformation, not copy-paste.
There is no native migration path between Podium and Crisp — no built-in import tool, no official adapter, and no click-to-migrate option exists. Podium operates on a location-based, multi-channel messaging model centered on SMS, reviews, and payments, while Crisp uses a website-based, session-centric model built around live chat and a shared inbox, resulting in fundamental data model mismatches. Custom API-based ETL pipelines are the only reliable approach for full-fidelity migration, requiring deliberate transformation of contacts, conversations, messages, tags, and metadata. Reviews, payments, and campaigns have no Crisp equivalent and must be archived externally or rebuilt manually.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
TL;DR: Podium → Crisp Migration
Podium is a customer interaction platform built around SMS messaging, reviews, and payments for local businesses. Crisp is a chat-first customer messaging platform for startups and SMBs. They share almost no structural overlap. Podium Contacts map to Crisp People Profiles. Podium Conversations become Crisp Conversations, but the session model is fundamentally different. Podium Locations map to Crisp Segments or custom data keys. Reviews, Payments, and Campaigns have no native Crisp equivalent — archive or discard them. There is no native migration path. Expect a custom API-based ETL pipeline as the only reliable approach for full-fidelity migration.
Reviews and Payments have no Crisp equivalent
If your Podium usage is heavily centered on review management or text-to-pay, Crisp is not a drop-in replacement for those functions. Archive this data before decommissioning Podium.
Crisp custom data keys must be lowercase with no special characters except underscores and dashes
Transform any Podium custom field names accordingly before import. Example: Preferred Contact Method → preferred_contact_method.
Contact Crisp support before starting a bulk conversation import
They can block outgoing email notifications from imported conversations so your customers don't receive messages for historical data. Also note: creating a conversation alone does not make it visible in the Crisp Inbox until a message is sent with from value user. Seed each session with the earliest inbound user message when possible.
Timestamp preservation is critical
When loading historical messages into Crisp, you must explicitly pass the original timestamp in the API payload. If omitted, Crisp will stamp every imported message with the current date and time, destroying your conversation timeline. Timestamps should be in Unix epoch milliseconds format. Verify the exact field name and expected format against the current Crisp API documentation.
Plugin tokens are not subject to per-minute rate limits — they use a daily quota instead,
Plugin tokens are not subject to per-minute rate limits — they use a daily quota instead, which is better suited for migration workloads. Request higher quotas from Crisp before starting your import. For a migration of 50K conversations, request a quota of at least 50,000 requests/day to complete the import within a reasonable window.
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 Crisp can hold your support model
Walk your current workflow through Crisp: 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 → Crisp 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 → Crisp specifics
- Cost compression
- Podium's pricing targets multi-location local businesses and currently routes buyers to a custom quote flow; published estimates place entry pricing at $399+/month. Crisp offers a free tier (2 seats), a Pro tier at $25/month per workspace (4 seats), and an Unlimited tier at $95/month per workspace (20 seats). For a 5-person support team running a single workspace, Crisp Unlimited costs ~$1,140/year vs. Podium's estimated $4,800+/year. (crisp.chat)
- Chat-first architecture
- Teams that interact primarily through website live chat and email — rather than SMS and review management — find Crisp's chat widget, chatbot builder, and shared inbox more aligned to their workflow.
- Developer accessibility
- Crisp provides official API wrappers for Python, Node.js, Ruby, and Go, plus an open-source conversation import tool. Podium's API requires a developer account application and approval process, which can take 2–5 business days.
- Simplified CRM
- Crisp bundles a lightweight CRM (contacts, segments, custom data, company attributes) directly into the messaging platform. Teams over-served by Podium's review and payment features but under-served on contact management often land here.
- Agency and SaaS use cases
- Crisp's multi-website management and plugin architecture appeal to agencies managing multiple client workspaces — a use case Podium's location-based model doesn't natively support.
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 -
Download attachments immediately during extraction
Podium attachment URLs expire after seven days (docs.podium.com)
Podium → Crisp specifics
- Contacts
- Total count, completeness (how many have email vs. phone only? In typical Podium accounts, 30–60% of contacts are phone-only)
- Conversations
- Total count, average messages per conversation, date range
- Locations
- Number of Podium locations, mapping strategy to Crisp
- Payments
- Volume, whether to archive or export separately
- Attachments
- File types and sizes in conversations (Crisp enforces a ~10 MB upload limit)
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 → Crisp 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 → Crisp 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 Crisp 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.
Podium → Crisp specifics
- Custom Fields
- Which of the 8 possible custom fields are in use?
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 Crisp sandbox that reconciles cleanly and has been reviewed by real agents.
Keep these open
-
Stand up a Crisp 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 Crisp'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 Crisp, 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 Crisp'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.
-
Delete imported conversations
via API (DELETE /v1/website/{website_id}/conversation/{session_id}) — must be done per-conversation
-
Delete imported contacts
via API (DELETE /v1/website/{website_id}/people/profile/{people_id})
-
Start with a fresh workspace
if contamination is too severe — create a new Crisp website and re-import
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 Crisp 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 Crisp, 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.
-
Rebuild automations
Re-create Podium automations as Crisp bot scenarios, chatbot flows, or triggers. Document the mapping between old Podium rules and new Crisp triggers.
-
Configure integrations
Reconnect any third-party tools (Shopify, CRMs, analytics) to Crisp. Point all webhooks away from Podium. Set up Crisp webhooks for any downstream systems that relied on Podium events.
-
Update website widgets
Replace Podium's webchat widget with Crisp's chatbox SDK. The Crisp chatbox requires adding a <script> tag with your CRISP_WEBSITE_ID to your site — remove the Podium widget script simultaneously to avoid conflicts.
Podium → Crisp specifics
- Train agents
- Crisp's shared inbox, shortcuts, and assignment model differ from Podium's location-based views. Ensure agents understand how to filter by segments and tags. Budget 2–4 hours for team onboarding on Crisp's interface.
- Decommission Podium only after validation
- Keep Podium active for at least 30 days post-migration as a reference and fallback.
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.
Concept Equivalent
| Podium field | Crisp field | Notes |
|---|---|---|
| Organization | Workspace (Website) | 1:1 if single-org; multi-org requires multiple Crisp workspaces |
| Location | Segment / Custom Data | Crisp has no native "location" object. Use segments or a podium_location custom data key |
| Contact | People Profile | Direct mapping. Email is the dedupe key in Crisp |
| Contact Tags | Segments | Podium tags → Crisp segments. Crisp does not publish a hard limit on segments per workspace or per contact, but performance degrades above ~500 segments per workspace in practice |
| Contact Custom Fields | Custom Data (key-value) | Podium allows up to 8 typed custom fields with picklist validation; Crisp uses free-form key-value pairs with no type enforcement |
| Conversation | Conversation | Structural mapping, but session models differ significantly |
| Message (SMS/Email/Webchat) | Message (text/file/note) | Message types require transformation |
| Internal Note | Note message (type: "note") | Only available on Crisp paid plans (Pro and above) |
| Review | ❌ No equivalent | Archive externally or discard |
| Payment | ❌ No equivalent | Archive externally or discard |
| Campaign | Campaign (Unlimited plan) | Manual rebuild required; no migration path for campaign content |
| Automation | Bot / Triggers | Manual rebuild required |
| Team Member / Agent | Operator | No programmatic bulk creation — operators must be invited via the Crisp dashboard or API individually |
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Contacts / People Profiles | medium | Direct structural mapping exists but Crisp requires email as the dedupe key, creating risk for phone-only Podium contacts that lack email addresses. |
| Conversations | high | Session models differ fundamentally — Podium ties conversations to locations while Crisp uses a website-workspace model — requiring significant structural transformation and custom API work. |
| Message History | high | Extracting and loading full message history requires hundreds of thousands of API calls constrained by Podium's 60-req/min rate limit, and each message type (SMS, email, webchat) needs transformation to Crisp's format. |
| Contact Tags / Segments | medium | Podium tags map to Crisp segments, but Crisp has no published hard limit and performance degrades above approximately 500 segments per workspace in practice. |
| Custom Fields | low | Podium allows up to 8 typed custom fields with picklist validation while Crisp uses free-form key-value pairs, making the mapping straightforward but losing type enforcement. |
| Internal Notes | medium | Internal notes map to Crisp's note message type but are only available on paid Crisp plans (Pro and above), requiring plan verification before migration. |
| Reviews | high | Crisp has no review management equivalent whatsoever, so all Podium review data must be archived externally or discarded entirely. |
| Payments | high | Crisp has no payment or text-to-pay functionality, meaning all Podium payment records must be exported and stored outside the destination platform. |
| Campaigns | medium | Crisp offers campaigns only on the Unlimited plan with no migration path for existing campaign content, requiring manual rebuild of all campaign logic and templates. |
| Automations / Bots | medium | Podium automations must be manually rebuilt as Crisp bot flows or triggers, with no programmatic migration path available between the two systems. |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
No Native Migration Path
Neither Podium nor Crisp provides a built-in migration tool or adapter between the two platforms, requiring a fully custom ETL pipeline using raw REST API calls.
Incompatible Session and Location Models
Podium ties conversations to physical business locations in a multi-location model, while Crisp uses a website-based workspace model with no native location object, requiring locations to be flattened into segments or custom data keys.
Podium API Rate Limits
Podium enforces a 60-requests-per-minute rate limit per OAuth app plus an undocumented daily envelope, meaning a dataset of 50K conversations with 15 messages each could require approximately 9.3 days of extraction time without parallelism.
Phone-Only Contacts Lack Email
Crisp uses email as the primary deduplication key for People Profiles and its CSV import requires an email address, but many Podium contacts are SMS-only with no email on file.
No Equivalent for Reviews and Payments
Podium's review management and text-to-pay functionality have no counterpart in Crisp, requiring teams to archive this data externally before decommissioning Podium.
Message Type Transformation Required
Podium messages span SMS, email, and webchat with channel-specific metadata, and must be transformed into Crisp's text, file, or note message types with different structural conventions.
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
Can I migrate conversation history from Podium to Crisp?
Yes, but only via the Crisp REST API or Crisp's open-source conversation import tool (crisp-import-conversations on GitHub). There is no CSV import for conversations in Crisp, and no native Podium adapter exists — you need a custom ETL pipeline to extract from Podium's API, transform the data, and load it into Crisp.
Does Crisp have a built-in Podium migration tool?
No. Crisp's official conversation import tool supports adapters for Zendesk, Gorgias, Help Scout, Tidio, GrooveHQ, and WHMCS — but not Podium. You would need to write a custom adapter or transform Podium data into Crisp's expected JSON schema.
What Podium data cannot be migrated to Crisp?
Reviews (Google/Facebook), Payments (text-to-pay), and Campaign content have no Crisp equivalent. These must be archived externally before decommissioning Podium. Automations and workflows also need to be manually rebuilt in Crisp.
How long does a Podium to Crisp migration take?
A contacts-only CSV migration takes a few hours. A full migration with conversation history typically takes 2–4 weeks of engineering effort, depending on data volume and complexity. Budget 80–160 engineer-hours for a mid-size dataset (10K–50K conversations) using a custom API pipeline.
How do I handle phone-only Podium contacts in Crisp?
Crisp uses email as the primary identifier for People Profiles. Phone-only contacts can exist in Crisp but won't merge with future chat sessions unless email is later added. You can assign a placeholder email or accept that these contacts will be orphaned from future sessions. Crisp's CSV import requires email, so phone-only records must go through the API.