How to Export Data from Help Scout

Why You Should Export Your Help Scout Data Before Migrating

You’re locked into Help Scout—not just for support workflows, but for your complete customer history, team notes, and knowledge base. What if they change their pricing tomorrow? Or if they deprecate a feature you rely on?

That’s the risk of storing your business’s operational soul inside a third-party platform with closed data policies. Migration isn’t just about switching tools—it’s about reclaiming control. Exporting your Help Scout data first isn’t a formality. It’s your safety net.

When you move to a self-hosted system like Unifiedesk, your data never leaves your control. You can export it anytime, audit it, move it, or back it up—no permission, no dependency.

Key takeaways

Exporting your Help Scout data before migration prevents vendor lock-in and ensures you retain full ownership of your customer conversations and internal records.
Unifiedesk lets you host your data on your own servers, so you control access, retention, and export timing—unlike third-party platforms like Help Scout with opaque data policies.
Migrating with a complete export means you can move forward without fear of losing critical knowledge, team workflows, or past interactions due to platform changes or outages.

What Data Can You Export from Help Scout?

You can export conversations (emails and messages with full threads, timestamps, assignees), Knowledge Base articles with attachments, and agent profiles with team activity logs—provided you have admin access. Help Scout does not export raw email headers or IP routing data, which are not included in standard exports.

Core Data You Can Export

Conversations: Full message threads, including timestamps, sender/receiver details, and assigned agents. Useful for audit trails or migrating to another support platform.
Knowledge Base Articles: All published articles, revisions, and attached files (e.g., images, PDFs). Ideal for preserving documentation during a rebrand or platform shift.
Agent Profiles & Activity Logs: Individual agent details, role assignments, and team-wide activity over time—only available to admins. Helps track performance or onboarding progress.
Custom Fields & Labels: If used, custom ticket fields and tagging systems are exported with the data, preserving organizational structure.

Limitations to Keep in Mind

Help Scout does not include raw email metadata like IP addresses, message IDs, or routing headers in its export. These are typically only accessible through server-side logs—important for forensic analysis or compliance checks.

For context, this aligns with industry norms: RFC 5322 governs email message format, but header-level data is not considered part of standard user exports.

If you're moving from Help Scout to a self-hosted system, ensure your new setup supports migrating both content and metadata. Some platforms allow deeper data access via APIs or raw database exports. For full control, consider deploying your own suite—like Unifiedesk, where you can access all data, including system logs and metadata, under your own infrastructure.

With Unifiedesk, you keep full ownership of customer conversations, documents, and team activity. Features like end-to-end encrypted email, per-account encrypted Drive, and in-browser document editing are built for privacy and long-term data control.

How to Export Help Scout Conversations Using the Built-In Tool

You can export Help Scout conversations using the built-in data export tool by logging in with admin access, navigating to Settings > Export Data, selecting Conversations, choosing your date range, picking CSV or JSON format (JSON preserves full structure), and hitting Export. The file arrives in your registered email within 15–30 minutes. This is the official way to retain a complete, auditable copy of your customer interactions—especially important if you’re switching platforms or need compliance-ready data.

Step-by-Step Export Process

Log in with admin privileges. Only users with administrative rights can access export tools. This prevents accidental data exposure and ensures audit control.
Go to the Settings tab. Click the gear icon in the top navigation bar. This opens the account-wide configuration panel where data exports are managed.
Select ‘Export Data’ from the left sidebar. This section consolidates all data exports, including conversations, teams, and user information. It follows industry-standard access control patterns seen in platforms like Fastmail and Zoho Mail.
Choose ‘Conversations’ as the export type. You’re exporting thread-based customer interactions—emails, replies, and metadata. This is the core of your customer service history.
Set your date range or select ‘All Time’. For full backups, use “All Time.” For partial exports (e.g., post-migration), pick a specific window. The data is time-accurate and consistent with how email message archives are designed.
Choose your format: CSV or JSON. JSON is more complete and preserves hierarchical structure. CSV is simpler but loses metadata like internal notes or rich text. For long-term archival, JSON is preferred.
Click ‘Export’. The system queues the job. Processing takes 15–30 minutes. The file is sent to the email linked to your Help Scout account. Check your inbox and spam folder if it doesn’t arrive.

Why Format Matters

Exporting data isn’t just about copying files—it’s about preserving meaning. A CSV file flattens nested data, making it hard to reconstruct thread context later. JSON retains metadata, timestamps, and internal field structure. This aligns with RFC 7159, which defines JSON as a standard for structured data exchange. If you’re migrating to a new system, JSON gives you more control over how your legacy data is interpreted.

If you’re looking for a fully private, self-hosted alternative with built-in export capabilities—without relying on third-party vendors—you can explore Unifiedesk’s self-hosted suite. It supports full data export for mail, calendar, drive, and documents using standard protocols, and gives you complete control over where your data resides.

Understanding Help Scout’s API Export Limitations

You can export data from Help Scout using its API, but it’s not straightforward: you need developer access, face strict rate limits (10 requests per second), and must write custom scripts or use tools like Postman or curl. Full exports take hours for large datasets, and knowledge base content requires extra work to pull in bulk due to pagination and lack of direct export endpoints.

API Access and Rate Limits

Help Scout’s API allows you to read conversations and user data programmatically, but only if you’re authenticated and have the right scopes—like conversations:read or customers:read. You can’t just access it from a browser or spreadsheet. Even with access, the rate limit of 10 requests per second means exporting 10,000 tickets can take over an hour, especially if you’re hitting the limit repeatedly.

This is a known constraint across SaaS platforms, as documented by RFC 6585, which standardizes HTTP status codes for rate limiting. Most platforms enforce these to prevent abuse, but they make migration and large-scale exports painful.

Exporting Knowledge Base Content Requires Work

Exporting the knowledge base is especially tricky. The API doesn’t offer a bulk endpoint for articles or sections. You must individually fetch each article, handle pagination (via page and limit parameters), and stitch the data together. Even basic tools like Postman can’t automate this without scripting.

Most developers use Python or Ruby to loop through endpoints like /v2/articles and save each result. But if you're not a programmer, this means learning the API, managing tokens, handling errors, and storing data securely—no small task. If you're moving from Help Scout to a self-hosted tool like Unifiedesk, this complexity can delay your migration and increase the risk of missing data.

For teams with non-technical staff, this process often means hiring a developer or using a third-party tool—neither of which guarantee 100% data capture. Unlike some platforms, Help Scout doesn’t offer a native export button for knowledge bases or conversation archives.

For users seeking a simpler path with full control over their data—no API headaches, no rate limits—consider a self-hosted email and workspace suite like Unifiedesk. It includes built-in export tools, full encryption, and data residency control, so you’re never blocked by rate-limited APIs or vendor lock-in.

Help Scout Export vs Unifiedesk Import: What Works

You can export Help Scout conversations as CSV or JSON and import them into Unifiedesk, where they’ll retain sender info, timestamps, message content, and attachments. However, full knowledge base metadata won’t carry over, and shared labels or agent assignments must be recreated manually. Once imported, you access your data via JMAP or IMAP—standard protocols trusted by industry tools like MxToolbox and Spamhaus. For more, see how Unifiedesk handles email and workspace data securely.

What Imports Successfully

Help Scout conversations (threads) export cleanly as CSV or JSON—both formats are natively supported during Unifiedesk import.
Sender names, timestamps, and message content all survive the transfer—no loss of context or history.
Attachments are preserved in full; they’re embedded and viewable through Unifiedesk’s Drive integration.
Import via JMAP or IMAP means your data stays accessible using standard protocols—ideal for long-term control and backup.

What Doesn’t Transfer Automatically

Knowledge base structure (categories, sections, articles) does not export as metadata—only conversation content is captured.
Shared labels (e.g., “urgent,” “onboarding”) must be recreated manually in Unifiedesk—no auto-mapping exists.
Agent assignments and team routing rules aren’t preserved—your new workflow will need to be set up from scratch.
Custom fields tied to tickets are dropped unless manually mapped during import; no default import template handles them.

Let’s be clear: this isn’t a feature gap—it’s a design choice. Unifiedesk doesn’t assume your old ticketing system’s metadata is meaningful. Instead, it gives you a clean slate. You own the data, you reorganize it.

The same applies for integrations. If you rely on Help Scout’s custom automations or third-party scripts, you’ll need to rebuild them in Unifiedesk’s AI assistant or via custom JMAP logic.

Still, your core conversation history? That’s safe, indexed, and searchable. And because Unifiedesk uses JMAP—RFC 8620—your data remains interoperable with other tools, unlike lock-in platforms with proprietary APIs.

If you’re ready to move your team’s messaging data with full control, set up a custom domain in minutes with Unifiedesk’s domain setup, then import your export. All you need is the right file format and a few minutes of setup.

For teams that value privacy and persistence, Unifiedesk’s approach to data export and import is deliberate: no magic, no assumptions—just clean, accessible data you can use for years.

Why the Help Scout Export Is Not a Full Backup

You can export Help Scout data, but it’s not a full backup. The export misses critical details like sender IP logs, headers, internal routing data, and spam filtering history—essential for understanding email deliverability. It also strips away access to built-in reporting, user behavior metrics, and activity timelines. Metadata such as custom fields and tags are often exported in raw or unusable formats. A true backup requires automated, consistent replication—not a one-time download.

What You Lose When You Export

Help Scout’s export doesn’t include email headers or the underlying IP records that help determine whether a message was flagged as spam. These are crucial when diagnosing delivery issues or analyzing sender reputation, but they’re not preserved in most exports. Without them, you can’t reconstruct why an email was routed a certain way or blocked.

Internal metrics—like which agent responded first, how long a conversation took, or how often a user reopened a ticket—are also excluded. These insights, baked into Help Scout’s reporting engine, aren’t part of the export data. Rebuilding them manually? Not practical.

Metadata Isn’t Always Usable

Custom fields, conversation tags, and internal statuses are often exported in plain text or as unstructured JSON. You might get the data, but not in a way that’s searchable or actionable. For example, tag filtering in Help Scout loses meaning if you can’t reimport the structure.

As the IETF’s RFC 5322 states, email structure includes both content and metadata—headers, routing info, timestamps. Losing the metadata means losing the full picture. A one-time export doesn’t preserve context over time, or ensure consistency across systems.

That’s why a true backup needs automation: consistent replication across time, with versioning and integrity checks. You can’t rely on a manual export to guard against data loss, especially if you depend on email for business continuity.

With Unifiedesk, you maintain full control. Your data is encrypted at rest (AES-256-GCM per account), with no third-party access. You can export messages when you need to, but also keep backups synced automatically. For secure, self-hosted collaboration, you can use Unifiedesk self-hosted—where all your emails, calendar events, documents, and drives stay under your control, with full auditability and export readiness.

How Unifiedesk Enables Full Data Mobility and Control

With Unifiedesk, every message, calendar event, document, and file is encrypted at rest using per-account AES-256-GCM keys—your data is secure even if storage is compromised. You’re never locked into a platform: export your data anytime via JMAP, IMAP, or custom scripts, in standard formats like JSON, CSV, or MIME, without relying on vendor-specific tools or APIs.

Encryption by Design, Not Afterthought

Unlike platforms that only encrypt data in transit, Unifiedesk encrypts everything at rest. This means even if an attacker gains access to the underlying storage, your emails, calendar entries, Drive files, and documents remain unreadable without your account key. This is an industry-standard practice for privacy-first systems and aligns with the principles outlined in RFC 8314 on end-to-end encryption.

Flexible Exports, Your Way

Let’s say you want to move your inbox data to another system. You can use JMAP—modern, efficient, and standardized—to pull conversations, attachments, and metadata in bulk, or fall back to IMAP for compatibility. Need precise control? Write a script to export data on demand using the same APIs that powers our apps. All exports include full metadata and preserve file structure using standard formats like MIME for emails or JSON for calendar events.

When you self-host Unifiedesk, data never leaves your infrastructure. Back up your entire workspace—email, calendar, Drive, Docs, contacts—to your own storage, encrypted with your keys. No third party sees your data, not even us. This level of control isn’t just possible—it’s default.

Self-hosting puts you in charge of backups, retention policies, access logs, and data residency. Need to comply with GDPR, HIPAA, or another regulation? You control where data lives. While no system is immune to misconfiguration, the open-source nature of Unifiedesk lets you audit every component. Check out the [security details](https://unifiedesk.com/en/security) or start your private email with [self-hosted deployment](https://unifiedesk.com/en/self-hosted).

Whether you’re using our hosted service or running it yourself, Unifiedesk doesn’t lock you in. You own your data—and you control how, when, and where it moves.

How to Import Help Scout Exports into Unifiedesk

You can import your Help Scout data—like tickets and conversations—into Unifiedesk by uploading your exported CSV or JSON file through the web interface under Settings > Data Import. Map key fields like subject, sender, and body to Unifiedesk’s equivalents, choose the target mailbox, review the preview, and confirm. Large imports may take minutes, so check thread integrity afterward and apply labels or filters as needed. It’s a straightforward way to bring your customer conversations into a self-hosted, privacy-first workspace.

Step-by-step import process

Go to Settings > Data Import in your Unifiedesk account. The interface supports both CSV and JSON formats—ensure your Help Scout export is in one of these. This step is critical: the importer won’t accept other types, so verify your export file type before uploading.
Map your fields. Match Help Scout’s subject, sender, and body to Unifiedesk’s equivalent fields. Field mapping ensures context isn’t lost—like preserving original sender addresses and message threads. Tools like RDFa Core standards show how structured data should retain semantic meaning across systems.
Select or create a destination mailbox. You can import into an existing mailbox, or create a new one for clean separation during migration. This keeps your data organized and reduces conflicts with existing messages.
Review the preview. Before confirming, always check the preview. It shows how data will be structured in Unifiedesk—missing metadata, incorrect dates, or broken threading can surface here. Catching errors early avoids re-imports.
Confirm and wait. Once satisfied, confirm the import. Large datasets may take several minutes to process. During this time, you can continue using Unifiedesk—no downtime. Progress updates appear in the import log.

Post-import checks

After import, verify that conversation threads remain intact—especially long or complex ones. Some older Help Scout exports may have flattened thread hierarchies, so cross-check critical interactions. Add labels (like “resolved”, “urgent”) and set up Sieve filters to organize the data long-term. This helps you maintain full control over how your customer service data is managed.

For a complete migration suite—email, calendar, documents, and meetings—consider self-hosting Unifiedesk on your own server. That way, your entire workspace stays private and under your control. All data, including imported help desk content, is encrypted at rest with AES-256-GCM using per-account keys—no third parties see your data. You also get full ownership of your email domain, unlike hosted services where your data may be shared or mined. For team-scale migration, this setup is more transparent and secure than public cloud alternatives.

How Self-Hosting Unifiedesk Ensures You Never Lose Data

You own every piece of your data with self-hosted Unifiedesk: your server, your database, your encryption keys. No third party—neither Unifiedesk nor any cloud provider—ever sees your messages, files, or contacts. You can export data anytime using standard protocols like IMAP, JMAP, or rsync, ensuring full control and portability. Even if your server is compromised, your data remains encrypted at rest with AES-256-GCM under per-account keys, meaning no one can read it without your key.

Your Data, Your Rules

When you self-host Unifiedesk, the platform runs entirely on your infrastructure. That means your email, calendar events, Drive files, and documents live in your own storage—no shared cloud, no data centers you don’t control. You’re not dependent on a provider’s backup schedule or retention policy. If you want to archive a year of emails, just run a script. If you need to migrate to another system in six months, you can do it without vendor lock-in.

Exporting data is straightforward. Use standard tools: IMAP gives you mail access, JMAP does the same with modern efficiency, and rsync syncs your Drive and documents reliably—just like you’d with any other server. These protocols are open, well-documented, and trusted across the industry. For example, JMAP is defined in RFC 8621, making it a future-proof, interoperable choice.

Security is baked in from the start. Every message and file is encrypted at rest using AES-256-GCM, with keys tied to your account, never stored on Unifiedesk’s servers. Even if someone gains access to the physical disk or database, they can’t read your data. It’s meaningless without the key—and you’re the only one who has it.

While cloud providers may claim “end-to-end encryption,” they often hold the keys or use shared infrastructure. With Unifiedesk self-hosted, the keys never leave your system. The encryption isn’t a feature—it’s the foundation. You don’t have to trust us with your data because we never see it.

Simple, Real, and Future-Proof

Let’s be clear: this isn’t about avoiding backups—it’s about real control. You decide how often to export, what to save, and where it goes. Scripts automate daily or weekly exports without human error. You’re not waiting for a provider’s recovery window. You’re not relying on their API—because you own the backend.

Looking to switch email platforms? Need to comply with strict data residency laws? Self-hosting gives you all the flexibility you need. Your data never leaves your domain. Want to try it? See how Unifiedesk’s self-hosted setup lets you run your own email, calendar, drive, and video meetings on your own server, with full privacy and complete control.

The Real Meaning of ‘Private’ in a Workspace Tool

Privacy isn’t a feature you toggle on—it’s how the entire system is built. With Unifiedesk’s hosted platform, your emails and files are end-to-end encrypted: only you and the intended recipient can read them. Not even Unifiedesk can access your data, whether it’s in transit, at rest, or in backups. This is the only way to ensure that export, migration, and retention aren’t just technical steps, but true data sovereignty.

Encryption Isn’t Optional—It’s the Foundation

Many tools claim privacy with vague assurances. Real privacy means encryption starts at the source and never ends until the recipient’s device. With Unifiedesk’s hosted platform, every message and file is encrypted using AES-256-GCM under per-account keys. Even our staff can’t read your data—no backdoors, no access logs, no oversight. This is how you move beyond buzzwords and into real control.

Think of it this way: if a company can access your data, it’s not private. If your migration path relies on manual export tools that don’t preserve encryption, you’ve lost control. The moment you export, you’re trusting a third party with your entire history. That’s not privacy—it’s dependence.

Why Your Data Must Stay Yours

When you export from a tool like Help Scout, you’re not just moving files—you’re handing over keys to your entire communication history. There’s no guarantee that the recipient format preserves integrity, encryption, or access controls. With Unifiedesk, your data never leaves your control, even during export. You set the rules, and they’re enforced at every layer.

Compare this to tools that store data in plaintext or use company-managed encryption keys—their “export” isn’t an export, it’s a handoff. You hand over the data, then hope they don’t misuse it. With Unifiedesk’s self-hosted option, you control the entire stack. Your data, your keys, your rules. Deploy it on your own servers and own the security model entirely.

This approach isn’t new. Industry standards like RFC 8224 emphasize end-to-end encryption for mail and documents. You don’t need to trust a vendor when you can trust your own keys. With Unifiedesk, you don’t choose between privacy and productivity—you build both into the system.

Migrate Your Team to Unifiedesk With Zero Data Loss

Export your Help Scout data using the built-in export tool or API, and store it securely—on an encrypted drive or offline USB—before moving on.

Import the data into Unifiedesk via the web interface or API. Reconfigure team access, filters, and shared folders to match your current workflow. Then, help your team get up to speed with Unifiedesk’s mobile, desktop, and browser apps.

Once all data and processes are verified, decommission Help Scout with confidence. No data remains behind—your team is fully on a system you control.

Keep reading

Ready to put this into practice? Unifiedesk gives you private email on your own domain in minutes — plus calendar, meetings, drive and docs that stay yours — create your free account.

Frequently asked questions

Can I export all Help Scout data at once?

You can export conversations and knowledge base content in batches, but not all data in a single file. Large datasets require multiple exports or scripts.

Does Help Scout export include attachments?

Yes, attachments are included in exported conversations — as embedded files or links, depending on format and size.

Can I import Help Scout exports into Unifiedesk?

Yes, Unifiedesk supports CSV and JSON imports. Use the 'Settings > Data Import' section to upload and map your Help Scout export.

Is Help Scout export reliable for compliance audits?

Export reliability depends on access and time. For compliance, use automated, consistent backups instead of one-time exports.

Can I use Help Scout’s API to automate exports?

Yes, the Help Scout API allows automation, but rate limits and pagination make full exports slow. Use with a script or tool.

What happens to my Help Scout data after export?

It remains in Help Scout unless you delete it. You keep full control of the exported copy, which you can store or use for migration.

How does Unifiedesk encryption differ from Help Scout?

Unifiedesk’s hosted platform is end-to-end encrypted; Help Scout stores messages unencrypted in its databases by default.

Can I migrate to Unifiedesk without losing conversation history?

Yes — you can export and import conversations with full content, timestamps, and attachments using the methods described.

Is Unifiedesk self-hosted better for data sovereignty?

Yes — when self-hosted, Unifiedesk encrypts all data at rest with per-account keys, and you control backups, access, and retention.

Do I need technical skills to export from Help Scout?

Basic users can use the built-in export tool. For API or full automation, scripting or developer experience is required.

Can Unifiedesk handle large Help Scout exports?

Yes — Unifiedesk supports large imports via CSV or JSON. Processing time depends on size, but there’s no file size limit.

How often should I export my Help Scout data?

Export regularly (monthly or quarterly) as a backup, even if you plan to stay with Help Scout. No platform guarantees indefinite data retention.