Unthread to Puzzel Case Management migration requires API-to-API extraction (paginated at 100/page), schema translation of Conversations→Tickets, Customers/Accounts→Organisations, and Ticket Types→Forms. No native path exists. Plan 2–4 weeks.
There is no native migration path between Unthread and Puzzel Case Management, and no third-party migration tool supports this specific pairing. Unthread's Slack-native, conversation-centric data model—built around Conversations, Customers, Accounts, Tags, and Ticket Types—must be structurally translated into Puzzel's contact-centre-oriented schema of Tickets, Organisations, Teams, Categories, Forms, and Form Fields, with no 1:1 entity mapping available. All data must be extracted via Unthread's REST API (paginated at 100 records with cursor-based iteration) and loaded into Puzzel one ticket at a time through API ticket channels, while Slack-proprietary markdown, user mentions, and threaded message hierarchies require custom transformation into standard HTML. Automations, SLA rules, and AI workflows cannot be migrated programmatically and must be rebuilt manually in Puzzel.
Read this first
Pair-specific gotchas that catch teams out. Each one has cost somebody a weekend.
TL;DR: Unthread → Puzzel Case Management Migration
An Unthread to Puzzel Case Management migration is a data-model translation from a Slack-native conversational helpdesk into a contact-centre-oriented ticketing system. There is no native migration path. Unthread has no bulk CSV export for ticket data — you must extract everything through the Unthread REST API (https://api.unthread.io/api/), paginated at 100 records per page with cursor-based iteration. On the Puzzel side, tickets are created one at a time through API ticket channels using Basic Token or OAuth authentication. Unthread's Conversations, Customers, Accounts, Ticket Types, and Tags do not map 1:1 to Puzzel's Tickets, Organisations, Teams, Categories, Forms, and Form Fields — each requires deliberate structural decisions. Automations, SLA rules, and AI workflows cannot be migrated programmatically and must be rebuilt manually. A typical mid-size migration (5,000–25,000 conversations) takes 2–4 weeks; in our experience, a 10,000-conversation migration with full thread history requires approximately 8–12 hours of API runtime plus 1–2 weeks of mapping, testing, and validation work.
Conditional field visibility is lost
Unthread's Ticket Type Fields support conditional visibility — a field can be shown or hidden based on another field's value using SimpleCondition logic (e.g., "Show field B only when field A = 'Billing'"). Puzzel's Form Fields do not have documented conditional logic. You'll need to flatten conditional fields into always-visible ones and document the original conditions for the receiving team. Consider adding a "(Conditional: only relevant when X = Y)" note in the field description.
Download attachments during extraction, not later
Slack-backed file URLs can expire within hours. If you extract the URL but wait to download, you'll get HTTP 403 Forbidden responses. Write files to disk or cloud storage (S3, GCS) before any transformation begins. Log all failures for manual follow-up.
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 Unthread
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 Puzzel Case Management can hold your support model
Walk your current workflow through Puzzel Case Management: 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 Unthread → Puzzel Case Management 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.
-
Contact centre consolidation
Puzzel Case Management integrates directly with Puzzel Contact Centre, unifying voice and written channels under one platform. Teams consolidating onto a full CCaaS stack need this integration to avoid operating parallel systems.
-
Record count comparison
Total conversations extracted vs tickets created in Puzzel. Tolerance: 0% — every conversation must be accounted for (migrated, skipped with reason, or failed with logged error).
Unthread → Puzzel Case Management specifics
- Email-first workflows
- Puzzel efficiently handles incoming support requests from email, SMS, and API integrations by categorising, prioritising, and routing them to agents based on their most relevant skills. Teams shifting away from Slack-native support toward traditional email ticketing with skill-based routing benefit from Puzzel's agent assignment engine.
- Regulated industry requirements
- Puzzel offers European-hosted infrastructure (data centres in the EU/EEA) and contact-centre-grade compliance capabilities including GDPR data retention controls and audit logging. Slack-native tools may not provide equivalent controls for industries with strict data residency or retention mandates (e.g., financial services, healthcare, government).
- Outgrowing Slack-first support
- As B2B support operations scale beyond ~10 agents into formal contact centre operations with unified workforce management, strict SLA enforcement across multiple channels (especially voice), and structured reporting, the move from conversational ticketing to structured case management becomes necessary.
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 Unthread 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 Unthread 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 Unthread 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 Unthread → Puzzel Case Management 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 Unthread → Puzzel Case Management 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 Puzzel Case Management 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.
Unthread → Puzzel Case Management specifics
- Status mapping
- Translate Unthread statuses to Puzzel equivalents (map closed to Resolved, not Closed)
- Priority mapping
- Unthread uses numeric priority (3, 5, 7, 9); map to Puzzel's priority scheme
- Customer/Account → Organisation
- Merge and deduplicate based on email domain and Slack channel ID
- Ticket Type → Form
- Create Forms in Puzzel with mapped Form Fields
- Slack mrkdwn → HTML
- Resolve user mentions, convert formatting (see Slack markdown table above)
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 Puzzel Case Management sandbox that reconciles cleanly and has been reviewed by real agents.
Keep these open
-
Stand up a Puzzel Case Management 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 Puzzel Case Management'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 Puzzel Case Management, 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 Unthread 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 Puzzel Case Management'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 Unthread 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 Unthread 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 Unthread and Puzzel Case Management 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 Puzzel Case Management, 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 Unthread 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.
Unthread → Puzzel Case Management specifics
- Message count validation
- For a random sample of 100+ tickets, verify thread depth (number of replies) matches source conversation message count.
- Attachment validation
- Confirm files are downloadable from Puzzel by requesting each attachment URL. Compare file sizes to source.
- Field-level spot checks
- Sample at least 5% of tickets (minimum 50) and compare every field value against source data.
- Status distribution
- Compare percentage breakdowns of open/closed/in-progress between source and target. These should match within 1%.
- Tag integrity
- Verify tag assignments match source data for sampled tickets.
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 Equivalent
| Unthread field | Puzzel Case Management field | Notes |
|---|---|---|
| Conversation | Ticket | 1:1 mapping. Status values need translation. |
| Message | Ticket reply / Internal note | Each message becomes a reply or internal note. Flag internal vs public based on metadata.eventType. |
| Customer (Channel) | Organisation | Unthread Customers are Slack channels; map to Puzzel Organisations. |
| Account | Organisation | Accounts may also map to Organisations. Deduplicate against Customers. |
| Tag | Tag | Direct mapping. Create tags in Puzzel first. |
| Ticket Type | Form | Each Ticket Type becomes a Puzzel Form. |
| Ticket Type Field | Form Field | Field types need translation (see below). |
| User (Agent) | User/Agent | Map by email address. Ensure agents exist in Puzzel before ticket import. |
| Knowledge Base Article | N/A (external) | Puzzel CM doesn't have a built-in KB. Export separately to an external tool. |
| File Attachment | Ticket Attachment | Download from Unthread during extraction, re-upload to Puzzel after ticket creation. |
Status Puzzel Equivalent
| Unthread field | Puzzel Case Management field | Notes |
|---|---|---|
| open | New / Open | Default for unassigned conversations. |
| in_progress | In Progress / Assigned | Use Assigned when assignedToUserId is populated. |
| on_hold | Pending | |
| closed | Resolved | Map to Resolved, not Closed. Closed tickets in Puzzel cannot be reopened. Use Closed only if your service model requires immutable closure (e.g., regulatory finality). |
Ticket Type Puzzel Form Equivalent
Unthread Ticket Type fields—particularly multi-user-select and conditional fields—do not map cleanly to Puzzel's Form Fields and require explicit per-field transformation logic.
| Unthread field | Puzzel Case Management field | Notes |
|---|---|---|
| short-answer | Text field | Direct mapping. |
| long-answer | Textarea / Multi-line text | Direct mapping. |
| single-select | Dropdown | Ensure option values match exactly. |
| multi-select | Multi-select dropdown | Verify Puzzel supports multi-select on the target Form. |
| checkbox | Checkbox | Direct mapping. |
| user-select | User dropdown (if supported) | Test in Puzzel sandbox; may require workaround. |
| multi-user-select | No direct equivalent | Serialize to comma-separated email list in a text field, or create multiple single-user fields. |
Unthread Puzzel CM
| Unthread field | Puzzel Case Management field | Notes |
|---|---|---|
| conversation.id | External Reference | Store as-is for traceability and idempotency |
| conversation.title | Ticket Subject | Direct map. Truncate to Puzzel's max subject length if needed. |
| conversation.status | Ticket Status | open→New, in_progress→Assigned, on_hold→Pending, closed→Resolved |
| conversation.priority (3,5,7,9) | Priority | 3→Critical, 5→High, 7→Medium, 9→Low |
| conversation.createdAt | Created Date | ISO 8601 direct map (UTC) |
| conversation.closedAt | Resolved Date | ISO 8601 direct map (UTC). Null if still open. |
| conversation.assignedToUserId | Assigned Agent | Map via users lookup table (Unthread userId → email → Puzzel agent) |
| conversation.tags [].name | Tags | Create tags in Puzzel first. Match by exact name. |
| conversation.ticketTypeId | Form | Map Ticket Type ID → Puzzel Form ID via mapping table |
| conversation.ticketTypeFields | Form Field values | Map field IDs to Form Field IDs. Handle type translation. |
| customer.name | Organisation Name | Direct map after deduplication |
| account.emailsAndDomains | Organisation custom attribute | Store as semicolon-delimited list or custom attribute |
| message.text | Reply body | Convert Slack mrkdwn → HTML, resolve user mentions, strip Block Kit |
| message.metadata.eventType | Note type indicator | internal_note → Internal note; all others → external reply |
| message.createdAt | Reply timestamp | ISO 8601 (UTC). Preserve original timestamp for audit trail. |
| files [].name | Attachment filename | Download from Unthread during extraction, re-upload to Puzzel after ticket creation |
Risk matrix
Per-object risk for this pair. Plan extra validation around anything marked high.
| Object | Risk | Notes |
|---|---|---|
| Tickets (Conversations) | high | Unthread conversations must be structurally translated into Puzzel tickets with no 1:1 mapping, and threaded Slack messages must be flattened into chronological interactions without losing reply context. |
| Message History | high | Each conversation's full message thread must be individually fetched via the API, and Slack markdown, user mentions, and Block Kit formatting require custom parsing to render correctly in Puzzel. |
| File Attachments | high | Slack-backed file URLs expire rapidly and return HTTP 403 errors after expiration, so all attachments must be downloaded proactively before cutover or they are permanently lost. |
| Custom Fields (Ticket Types) | high | Unthread Ticket Type fields—particularly multi-user-select and conditional fields—do not map cleanly to Puzzel's Form Fields and require explicit per-field transformation logic. |
| Customers / Contacts | medium | Customer records must be mapped to Puzzel Contacts and Organisations, but Unthread's Slack-user-based customer identity model differs from Puzzel's email-centric contact structure. |
| Accounts / Organisations | medium | Unthread Accounts must be translated into Puzzel Organisations with appropriate contact associations, requiring deduplication and relational integrity checks. |
| Tags and Categories | medium | Unthread Tags must be mapped to Puzzel Categories, which may have different hierarchy and cardinality constraints requiring consolidation or restructuring. |
| Automations and SLA Rules | high | No programmatic migration path exists for automations, SLA rules, or AI workflows—all must be manually audited and rebuilt from scratch in Puzzel. |
| Knowledge Base Articles | medium | Articles require extraction from Unthread and reformatting for Puzzel's content structure, with embedded media and internal links needing manual review. |
| Agent / Team Assignments | low | Agent and team structures are relatively straightforward to recreate in Puzzel's Teams configuration, though Slack-based user IDs must be mapped to Puzzel agent identities. |
The hard parts
What makes this specific migration difficult, beyond the mechanics.
No Native Export Path
Unthread lacks a bulk CSV export for ticket data, requiring all extraction to be performed through its REST API with cursor-based pagination at 100 records per page.
Incompatible Data Models
Unthread's Conversations, Customers, Accounts, Tags, and Ticket Types do not map 1:1 to Puzzel's Tickets, Organisations, Teams, Categories, Forms, and Form Fields, requiring deliberate structural translation decisions for each entity.
Slack Markup Translation
Slack-proprietary formatting including user mentions (<@U12345>), channel references, and Block Kit markup must be parsed and converted into standard HTML to avoid rendering as raw text in Puzzel.
Thread Flattening Complexity
Hierarchical Slack conversation threads must be flattened into chronological ticket interactions while preserving reply chains and the distinction between internal and external messages.
Attachment URL Expiration
Slack-backed file URLs used by Unthread typically expire within hours, requiring all attachments to be downloaded and re-uploaded before cutover to avoid permanent data loss.
Automation and SLA Rebuild
Automations, SLA rules, and AI workflows from Unthread cannot be migrated programmatically and must be manually recreated within Puzzel's configuration framework.
Tools used in this playbook
All free, all run entirely in your browser — nothing is uploaded.
FAQ
Can I export data from Unthread as CSV?
No. Unthread does not offer a native CSV export for ticket data. All data extraction must go through the Unthread REST API (api.unthread.io/api/). List endpoints are paginated at 100 records per page using cursor-based pagination. You'll need a script to extract conversations, messages, customers, accounts, tags, and ticket types via POST /list endpoints.
Does Puzzel Case Management support bulk ticket import via API?
Puzzel Case Management supports ticket creation through API ticket channels configured in Settings > Ticket Channels > API with Basic Token or OAuth authentication. Tickets are created one at a time — there is no documented bulk import endpoint, so you'll need to loop through records with rate-limit handling.
How long does an Unthread to Puzzel migration take?
A typical mid-size migration (5,000–25,000 conversations) takes 2–4 weeks: 2–3 days for planning and mapping, 3–5 days for extraction, 3–5 days for transformation and test loading, 2–3 days for production loading and delta sync, and 2–3 days for validation and cutover. Smaller datasets under 1,000 conversations can be completed in 1–2 weeks.
What data is lost when migrating from Unthread to Puzzel?
You'll lose Slack-native threading context (threads become flat replies), Slack Block Kit formatting (must convert to HTML), conditional Ticket Type Field visibility logic, the built-in Knowledge Base (Puzzel CM has no native KB), AI auto-resolution workflows, and Slack-specific metadata like channel IDs and thread timestamps. Automations and SLA rules must be rebuilt manually in Puzzel's Event Rules.
Is there a third-party tool that migrates Unthread to Puzzel automatically?
No. At the time of writing, no third-party migration tool supports the Unthread-to-Puzzel Case Management pairing natively. You'll need either custom API scripts, a middleware platform like Pipedream for small ongoing syncs, or a managed migration service.