Migrate your Fernand data
AI-powered helpdesk for SaaS teams that prioritizes keyboard-driven speed and a calm inbox experience over feature sprawl.
In its favor
Why people choose Fernand
The signal that keeps Fernand on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Low per-seat price at $29/active user with all features included removes upgrade friction for growing SaaS teams.
Keyboard-first interface and Linear-style UX appeals to technical teams who prefer speed over feature breadth.
AI-assisted reply drafting reduces agent handle time on repetitive queries, directly improving response metrics.
GitHub and Linear integrations create a tight feedback loop between support conversations and engineering work.
14-day free trial with no credit card required means teams can validate fit before committing any budget.
Small review base makes it hard to assess long-term reliability compared to more established helpdesk platforms.
Limited integrations beyond GitHub, Linear, and Stripe may constrain teams needing deeper CRM or telephony connections.
Smaller vendor risk for bootstrapped teams who worry about product continuity and long-term support availability.
Reasons to switch
Why people leave Fernand
The recurring reasons buyers give for replacing Fernand. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Fernand 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
Fernand pricing overview
Fernand uses a single flat plan at $29 per active user per month. Active users are those who can respond directly to customers; passive collaborators are free and unlimited. All features are included with no tier-based restrictions. No annual discount or enterprise tier is publicly documented.
Single Plan
Tier 1 of 1
$29/active user/month
What's included
Need help selecting your Helpdesk?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Fernand's schedule — see our quote-based pricing →
What gets migrated
Fernand object support
Object-by-object support for Fernand migrations. Per-pair details surface during scoping.
Conversations
Fully supportedConversations are the primary ticket object in Fernand. We export full conversation metadata including status, priority, assignee, and timestamps. Fernand does not appear to expose a public bulk-export endpoint; we use the available API with Bearer token auth to pull conversation records in batches.
Replies
Fully supportedReplies are threaded within conversations. We preserve the full reply body, author, creation timestamp, and internal/external status flag during migration. AI-generated draft replies are included if they were saved.
Customers
Mapping requiredCustomers are contacts associated with conversations. We export name, email, and any custom properties. Email addresses are used as the primary key for deduplication at the destination. Any Fernand-specific customer fields require manual mapping to the target system's contact schema.
Custom Data
Mapping requiredCustom Data in Fernand fetches external API responses per conversation. This is configuration-level data (API endpoint URLs, header names) plus the fetched payloads. We export the payloads as conversation notes or custom fields depending on destination capability. The API endpoint configuration itself does not migrate.
Users/Agents
Mapping requiredActive users (those who can reply to customers) and passive users (collaborators) exist in Fernand. We export user name, email, and active/passive status. Passive users without a destination equivalent are mapped to read-only roles.
Tags
Fully supportedConversations can be tagged in Fernand. We preserve all tag names and apply them as labels or tags at the destination. Tag counts and usage frequency are retained.
GitHub Links
Mapping requiredGitHub integration links conversation threads to issues and can auto-reopen conversations when issues change status. We export the linked GitHub issue URL and status as a custom conversation field since the destination likely does not have native GitHub sync.
Linear Links
Mapping requiredLinear integration creates a similar feedback loop to GitHub. We export the linked Linear issue reference as a conversation field. Issue state sync does not carry over as the destination lacks the integration.
Attachments
Fully supportedFile attachments on conversations and replies are downloaded and re-uploaded to the destination. Image attachments sent via the widget are included. We preserve original filenames and MIME types.
Channels
Mapping requiredFernand supports email and chat channels. We export channel type per conversation. The mapping to destination channel types depends on what channels the destination supports.
| Object | Support | Notes |
|---|---|---|
| Conversations | Fully supported | Conversations are the primary ticket object in Fernand. We export full conversation metadata including status, priority, assignee, and timestamps. Fernand does not appear to expose a public bulk-export endpoint; we use the available API with Bearer token auth to pull conversation records in batches. |
| Replies | Fully supported | Replies are threaded within conversations. We preserve the full reply body, author, creation timestamp, and internal/external status flag during migration. AI-generated draft replies are included if they were saved. |
| Customers | Mapping required | Customers are contacts associated with conversations. We export name, email, and any custom properties. Email addresses are used as the primary key for deduplication at the destination. Any Fernand-specific customer fields require manual mapping to the target system's contact schema. |
| Custom Data | Mapping required | Custom Data in Fernand fetches external API responses per conversation. This is configuration-level data (API endpoint URLs, header names) plus the fetched payloads. We export the payloads as conversation notes or custom fields depending on destination capability. The API endpoint configuration itself does not migrate. |
| Users/Agents | Mapping required | Active users (those who can reply to customers) and passive users (collaborators) exist in Fernand. We export user name, email, and active/passive status. Passive users without a destination equivalent are mapped to read-only roles. |
| Tags | Fully supported | Conversations can be tagged in Fernand. We preserve all tag names and apply them as labels or tags at the destination. Tag counts and usage frequency are retained. |
| GitHub Links | Mapping required | GitHub integration links conversation threads to issues and can auto-reopen conversations when issues change status. We export the linked GitHub issue URL and status as a custom conversation field since the destination likely does not have native GitHub sync. |
| Linear Links | Mapping required | Linear integration creates a similar feedback loop to GitHub. We export the linked Linear issue reference as a conversation field. Issue state sync does not carry over as the destination lacks the integration. |
| Attachments | Fully supported | File attachments on conversations and replies are downloaded and re-uploaded to the destination. Image attachments sent via the widget are included. We preserve original filenames and MIME types. |
| Channels | Mapping required | Fernand supports email and chat channels. We export channel type per conversation. The mapping to destination channel types depends on what channels the destination supports. |
Gotchas
What to watch for in Fernand migrations
Issues we've hit on past Fernand migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Fernand has no documented bulk export endpoint
Custom Data configuration does not migrate as code
GitHub and Linear sync state does not carry over
| Severity | Issue |
|---|---|
| High | Fernand has no documented bulk export endpoint |
| Medium | Custom Data configuration does not migrate as code |
| Medium | GitHub and Linear sync state does not carry over |
Leaving Fernand?
Where Fernand customers move next
7 destinations Fernand can migrate to.
How a Fernand migration works
Four steps, Fernand-specific
Connect
Bearer token into Fernand. Scopes limited to read-only on the data we move.
Map
We translate Fernand-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Fernand quirks before production.
Migrate
Full migration with Fernand rate-limit handling. Rollback available throughout.
FAQ
Fernand migration FAQ
Answers to the questions buyers ask most during Fernand migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Fernand 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 Fernand.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Fernand setup and destination — written quote back within a business day.