Podium and Freshservice have no native migration path. Use API-based ETL or a managed service — CSV exports only cover contacts and miss conversation history.
There is no native migration path between Podium and Freshservice, as the two platforms share almost no structural overlap—Podium is a customer interaction platform built around messaging, reviews, and payments, while Freshservice is an ITIL-aligned IT service management platform for ticketing, asset management, and change control. The fundamental data model mismatch is structural: Podium is location-centric with open-ended conversation threads, whereas Freshservice is requester-centric with strict ticket lifecycles. Migration requires a custom API-based ETL pipeline, FTP raw data extraction, or a managed migration service, as CSV exports from Podium omit conversation threading, attachments, and relational context.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
Freshservice custom fields are not included in ticket exports by default
When importing, you must pre-create all custom fields in the Freshservice Field Manager before CSV upload, or values will be silently dropped.
Archive reviews, payments, and campaign data to a data warehouse or CSV backup before migration
This data has no target in Freshservice, but you may need it for compliance or analytics.
Freshservice supports Custom Objects on Enterprise plans, but they are narrower than a CRM schema
Identity fields must be text, lookups are constrained, and paragraph fields cannot be used as workflow filters. Plan capacity before adding Podium-specific metadata fields. (support.freshservice.com)
Freshservice email uniqueness is enforced across both agents and requesters
If a Podium contact's email already exists as an agent in Freshservice, the requester creation call will fail silently or return a non-obvious error. Pre-check the agent list before bulk importing requesters.
Freshservice's partner bulk APIs do not turn off workflows for you
Some end-user notifications are suppressed, but workflow rules still run unless you guard them first. (support.freshservice.com)
Podium message attachment URLs expire after 7 days
Download attachment binaries during extraction, not after mapping QA. (docs.podium.com)
If you did not disable workflow automations before loading migrated data, check for
If you did not disable workflow automations before loading migrated data, check for unintended notifications or auto-assignments triggered by the import.
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 Freshservice can hold your support model
Walk your current workflow through Freshservice: 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 → Freshservice 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 → Freshservice specifics
- Operational maturity
- Podium is designed for external customer messaging — SMS, webchat, and review management. When support operations grow beyond "reply to texts" into structured incident management, SLA enforcement, and change control, Freshservice is the natural destination.
- ITSM requirements
- Podium has no concept of incidents, problems, changes, or releases. Freshservice provides full ITIL lifecycle support with configurable workflows, approval chains, and a built-in CMDB.
- Consolidation
- Teams using Podium alongside a separate ITSM tool often consolidate into Freshservice to reduce tool sprawl, especially after acquisitions or operational restructuring. MSPs and agencies using Podium for client communication frequently outgrow it, needing Freshservice's Department (Company) and Asset (CI) management.
- SLA management
- Podium lacks strict SLA policies, escalation matrices, and routing rules required for mature support operations.
- Transition period, ongoing sync
- Middleware for new records plus API or managed service for historical backfill.
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 → Freshservice 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 → Freshservice 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 Freshservice 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.
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 Freshservice sandbox that reconciles cleanly and has been reviewed by real agents.
Keep these open
-
Stand up a Freshservice 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 Freshservice'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 Freshservice, 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 Freshservice'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.
Podium → Freshservice specifics
- Cutover strategy
- Big bang (single switch) vs. phased (contacts first, then conversations) vs. parallel run (both systems live during transition).
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 Freshservice 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 Freshservice, 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.
Object Typical Volume
| Podium field | Freshservice field | Notes |
|---|---|---|
| Contacts | 100s–100,000s | Core records — map to Freshservice Requesters |
| Conversations/Messages | 1,000s–1,000,000s | Map active/recent conversations to Tickets |
| Leads | 100s–10,000s | Map to Tickets with category tag |
| Reviews | 100s–10,000s | No Freshservice equivalent |
| Review Invites | 100s–10,000s | No Freshservice equivalent |
| Feedback/Surveys | 100s–1,000s | Export for records, don't migrate |
| Payments | 100s–10,000s | No Freshservice equivalent |
| Campaigns | 10s–100s | Rebuild marketing in another tool |
| Campaign Contacts | 100s–100,000s | Opt-in/opt-out records for compliance |
| Locations/Organizations | 1–100s | Map to Departments |
Podium Freshservice
| Podium field | Freshservice field | Notes |
|---|---|---|
| contact_uid | requester.id (auto-generated) | Store mapping: Podium UID → FS ID in custom field podium_contact_uid |
| contact_name | requester.first_name, requester.last_name | Split on first space; handle single-name contacts |
| channel_unique_identifier (phone) | requester.mobile_phone_number | Normalize to E.164 format |
| channel_unique_identifier (email) | requester.primary_email | Lowercase, trim whitespace, deduplicate |
| organization_name / location_name | department.name | Create departments before requesters |
| conversation_uid | ticket custom field podium_conversation_uid | Store mapping for reruns |
| conversation_item_body | ticket.description (first) / ticket.note.body (rest) | HTML-encode if needed |
| conversation_inserted_at | ticket.created_at | ISO 8601 — must be explicitly passed in API payload |
| conversation_is_closed | ticket.status | true → 5 (Closed), false → 2 (Open) |
| conversation_channel_type | ticket.source | phone → 3, email → 1, webchat/secure → 2 |
| conversation_assigned_user_uid | ticket.agent_id | Requires agent UID → Freshservice agent ID mapping |
| contact_channel_marketing_opted_in_source | Custom requester field | Preserve for TCPA/GDPR compliance |
| review_rating | N/A | Archive — no Freshservice equivalent |
| invoice_amount_dollars | N/A | Archive — no Freshservice equivalent |
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Contacts / Requesters | medium | Podium contacts can be exported via CSV or API, but polymorphic identifiers (phone, email, conversation UID) require deduplication and field mapping to Freshservice's requester schema. |
| Conversations / Tickets | high | Podium's open-ended messaging threads have no structural equivalent to Freshservice's lifecycle-driven tickets, requiring custom state mapping, threading reconstruction, and explicit status assignment. |
| Messages / Ticket Replies | high | Individual messages within Podium conversations must be extracted via paginated API calls subject to strict rate limits and then mapped to Freshservice ticket replies or notes with correct chronological ordering. |
| Attachments | high | Attachments are not included in Podium CSV exports and must be individually retrieved via the API, then re-uploaded to Freshservice tickets, with risk of broken references or missing files. |
| Custom Fields | medium | Freshservice requires all custom fields to be pre-created in Field Manager before import; values mapped to non-existent fields are silently dropped without error notification. |
| Organizational Hierarchy | medium | Podium's Location → Organization structure must be remapped to Freshservice's Department → Company model, which follows a different hierarchy and scoping logic. |
| Reviews and Feedback | low | Freshservice has no equivalent for Podium's reviews, review invites, or feedback surveys, so these entities must be archived externally rather than migrated. |
| Payment Records | low | Podium invoices and payment records have no Freshservice equivalent and should be exported to an external archive or financial system rather than included in migration scope. |
| Leads / Sales Pipeline | low | Podium's inbound lead conversations have no counterpart in Freshservice's service-oriented model and must be either discarded or archived outside the ITSM platform. |
| Tags and Metadata | medium | Podium contact tags and conversation metadata need to be mapped to Freshservice requester custom fields or ticket tags, with risk of data loss if the target taxonomy is not pre-configured. |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
Location-Centric vs Requester-Centric Models
Podium organizes all data around location UIDs while Freshservice ties tickets to requesters within departments, requiring a complete restructuring of organizational hierarchies during migration.
Conversation-to-Ticket State Mapping
Podium conversations are open-ended messaging threads with no formal lifecycle, while Freshservice tickets enforce strict status workflows (Open → Pending → Resolved → Closed), requiring explicit state mapping logic.
No Equivalent Data Entities
Podium features like reviews, review invites, feedback surveys, payment records, and sales leads have no counterpart in Freshservice and must be archived externally or discarded.
API Rate Limit Constraints
Podium's message endpoints are capped at 10 requests per minute and Freshservice rate limits vary by plan (100–500 requests/min), creating potential multi-day load windows for large datasets.
Polymorphic Contact Identity Resolution
Podium contacts are identified by a mix of conversation UIDs, email addresses, and phone numbers, making deduplication and mapping to Freshservice's single-requester model error-prone.
Conversation Threading and Attachment Loss
CSV exports from Podium exclude conversation history, message threading, and file attachments, meaning any non-API migration approach loses critical relational context.
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
Can I migrate Podium conversations to Freshservice tickets?
Yes, but only through the Podium REST API or FTP raw data export. Each Podium conversation maps to one Freshservice ticket, with the first message becoming the ticket description and subsequent messages becoming ticket notes or replies. CSV exports do not include conversation history.
What Podium data cannot be migrated to Freshservice?
Reviews, review invites, feedback surveys, payment records, and campaign analytics have no equivalent objects in Freshservice. These should be archived to CSV or a data warehouse before migration.
What are the Freshservice API rate limits for data migration?
Freshservice enforces account-wide minute-level rate limits: 100/min on Starter, 200/min on Growth, 400/min on Pro, and 500/min on Enterprise. Add-on packs can increase limits up to 2,000/min. A separate gated bulk migration API exists for migration partners but only covers tickets and notes.
How do I handle Podium contacts with only phone numbers in Freshservice?
Freshservice strongly prefers email for requester identification and ticket routing. For phone-only Podium contacts, generate a placeholder email (e.g., +15551234567@podium-migrated.internal) or use the phone number field and accept limited ticket routing functionality.
How long does a Podium to Freshservice migration take?
For contacts-only via CSV, a few hours. For full API-based migration with conversations, expect 2–5 days of engineering work for script development plus load time dependent on data volume and Freshservice API rate limits. A managed migration service typically completes in 3–7 days.