Migrate your Foqal data
Slack and Microsoft Teams-native ticketing and workflow automation platform for IT, HR, and customer support teams. Turns messaging channels into structured support operations with AI-powered routing and reporting.
In its favor
Why people choose Foqal
The signal that keeps Foqal on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Messaging-native support that eliminates the need for a separate support portal — agents and customers stay in Slack or Teams where they already communicate.
Fast setup with a 30-day trial that installs directly into an existing Slack workspace without requiring customers to change their communication habits.
AI-powered ticket routing and automated responses reduce manual triage for IT and HR teams handling high-volume internal requests.
Reported CSAT improvements and cost-per-ticket reductions cited by high-growth tech companies moving away from email-based support.
Built-in HubSpot integration syncs Companies, Deals, and Contacts automatically, giving customer success teams full context inside messaging channels.
Small vendor with limited company scale (1–10 employees) raises concerns about long-term support continuity and product roadmap stability.
The conversational ticketing model loses structure when migrated out — automation rules, workflow triggers, and SLA configurations are not fully portable to traditional helpdesk platforms.
Alternatives like Zendesk, Salesforce Service Cloud, and Zoho Desk offer more mature feature sets, larger ecosystems, and stronger enterprise-grade guarantees.
Rate limits and API restrictions are not publicly documented, making it difficult to plan bulk migrations or automate large-scale data exports reliably.
No public pricing transparency for Enterprise tier creates uncertainty for organizations that need predictable cost scaling.
Reasons to switch
Why people leave Foqal
The recurring reasons buyers give for replacing Foqal. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Foqal fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Foqal pricing overview
Foqal uses a per-agent monthly subscription model. The Free tier is heavily limited for team growth, Premium starts at $50 per agent per month, and Enterprise pricing requires direct sales engagement with custom contract terms.
Free
Tier 1 of 3
Free
What's included
Need help selecting your Helpdesk?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Foqal's schedule — see our quote-based pricing →
What gets migrated
Foqal object support
Object-by-object support for Foqal migrations. Per-pair details surface during scoping.
Tickets
Fully supportedCore Foqal object. Tickets are created in Slack/Teams channels and carry status, priority, assignee, and timestamps. The API returns tickets with full metadata. We migrate tickets 1:1 with all standard fields intact.
Conversations
Fully supportedConversation threads are attached to tickets. Each message is timestamped and attributed to a user or agent. We preserve the full thread chronology and attachment references during migration.
Agents
Mapping requiredAgent records include name, email, role, and team assignment. We map agent identities to user records in the destination, handling cases where the destination uses a different user-object schema.
Teams
Mapping requiredTeams group agents and own specific SLAs and routing rules. Team membership and team-level settings require explicit mapping to the destination's equivalent grouping structure.
Workflows
Mapping requiredFoqal automations (routing rules, approval chains, SLA policies) are config-level records. We export workflow definitions and recreate equivalent automation in the destination platform, as workflows are not always represented as data objects in the API.
Approval Requests
Mapping requiredApprovalRequest objects use a URN identifier format (ApprovalRequestUrn). These are referenced by workflow approvals and must be reconstructed in the destination with updated URN references.
SLA Policies
Mapping requiredSLA configurations (TTFR, wait times, tier definitions) are stored as settings. We export the SLA policy definitions and map them to the destination's SLA model, noting tier-level differences between Enterprise, Premium, and Free plans.
Integrations
Mapping requiredHubSpot sync (Companies, Deals, Notes, Users), Jira sync, and ServiceNow sync are connection-level configs. We capture which records are linked and migrate the relationship pointers, not the third-party data itself.
Reports and Metrics
Not in this platformFoqal's productivity and CSAT reporting is computed from ticket data at query time. The reports themselves are not exportable as standalone data objects. We do not migrate report snapshots; the destination platform will generate its own analytics from migrated ticket data.
| Object | Support | Notes |
|---|---|---|
| Tickets | Fully supported | Core Foqal object. Tickets are created in Slack/Teams channels and carry status, priority, assignee, and timestamps. The API returns tickets with full metadata. We migrate tickets 1:1 with all standard fields intact. |
| Conversations | Fully supported | Conversation threads are attached to tickets. Each message is timestamped and attributed to a user or agent. We preserve the full thread chronology and attachment references during migration. |
| Agents | Mapping required | Agent records include name, email, role, and team assignment. We map agent identities to user records in the destination, handling cases where the destination uses a different user-object schema. |
| Teams | Mapping required | Teams group agents and own specific SLAs and routing rules. Team membership and team-level settings require explicit mapping to the destination's equivalent grouping structure. |
| Workflows | Mapping required | Foqal automations (routing rules, approval chains, SLA policies) are config-level records. We export workflow definitions and recreate equivalent automation in the destination platform, as workflows are not always represented as data objects in the API. |
| Approval Requests | Mapping required | ApprovalRequest objects use a URN identifier format (ApprovalRequestUrn). These are referenced by workflow approvals and must be reconstructed in the destination with updated URN references. |
| SLA Policies | Mapping required | SLA configurations (TTFR, wait times, tier definitions) are stored as settings. We export the SLA policy definitions and map them to the destination's SLA model, noting tier-level differences between Enterprise, Premium, and Free plans. |
| Integrations | Mapping required | HubSpot sync (Companies, Deals, Notes, Users), Jira sync, and ServiceNow sync are connection-level configs. We capture which records are linked and migrate the relationship pointers, not the third-party data itself. |
| Reports and Metrics | Not in this platform | Foqal's productivity and CSAT reporting is computed from ticket data at query time. The reports themselves are not exportable as standalone data objects. We do not migrate report snapshots; the destination platform will generate its own analytics from migrated ticket data. |
Gotchas
What to watch for in Foqal migrations
Issues we've hit on past Foqal migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Import from Zendesk and HappyFox requires manual arrangement
Workflow automation rules are not first-class API objects
Free plan severely limits agent seats and features
Origin header requirement blocks cross-origin API access
| Severity | Issue |
|---|---|
| High | Import from Zendesk and HappyFox requires manual arrangement |
| Medium | Workflow automation rules are not first-class API objects |
| Medium | Free plan severely limits agent seats and features |
| Low | Origin header requirement blocks cross-origin API access |
Leaving Foqal?
Where Foqal customers move next
7 destinations Foqal can migrate to.
How a Foqal migration works
Four steps, Foqal-specific
Connect
Bearer token (dashboard-generated under Settings > Users) into Foqal. Scopes limited to read-only on the data we move.
Map
We translate Foqal-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Foqal quirks before production.
Migrate
Full migration with Foqal rate-limit handling. Rollback available throughout.
FAQ
Foqal migration FAQ
Answers to the questions buyers ask most during Foqal migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Foqal migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationOther helpdesks we support
Ready when you are
Migrate Foqal.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Foqal setup and destination — written quote back within a business day.