Move data between workspaces

How to move data from one Quackback workspace to another: what the workspace export contains, what can be imported today, and how.

There's no one-click transfer between two Quackback workspaces, but you can move most of your data with an export and an import. This article explains what the workspace export contains, which parts you can bring into another workspace today, and how.

Short answer

Posts move with the built-in CSV import.
Users, changelog entries, help center articles, and tickets can be recreated through the REST API.
Comments and votes can be brought over with the open-source command-line importer.
Support conversations can't be imported. Keep the export as an archive.
Settings (boards, statuses, tags, branding, access rules, integrations) are set up again by hand. Boards, statuses, and tags named in your posts file are created automatically during the import.

Step 1: Export the source workspace

In the source workspace, go to Settings > Imports & exports.
Under Export workspace data, click Export.
When the run shows Completed, download the ZIP. The link expires after 7 days.

The ZIP contains boards.csv, statuses.csv, tags.csv, posts.csv, post_comments.csv, post_votes.csv, users.csv, companies.csv, conversations.jsonl, changelog.csv, kb_articles.csv, and manifest.json. See Import and export data.

Note: On Quackback Cloud, the workspace export is available from the Business plan. To move only feedback, you can export each board as CSV from its Data tab instead (also Business on Cloud).

Step 2: Prepare the destination workspace

In the destination workspace, create at least one board and review your statuses. Set up branding, portal access, and integrations the way you want them.

Step 3: Import posts

posts.csv already uses the import template's columns (title, content, status, tags, board, author_name, author_email, vote_count, created_at).

Open posts.csv in a spreadsheet and rename the id column to source_id. This lets you re-run the import without creating duplicates.
In the destination workspace, go to Settings > Imports & exports and import the file.
Check the preview, then commit.

Statuses are matched by name or slug, and boards by slug. Anything missing is created. Post authors are matched by email or created; an author with only a name becomes a name-only contact. Each post keeps its vote count, but not the individual voters.

Step 4: Bring over the rest (optional)

Comments and voters

The open-source Quackback repository on GitHub includes a command-line importer (scripts/import) that reads separate CSV files for posts, comments, votes, and internal notes and writes them through the REST API with an API key from Settings > Developers. Map post_comments.csv and post_votes.csv onto its column format. Its README describes each file.

Users, changelog, and help center

Use the REST API in the destination workspace:

Users: create or update each user from users.csv with the users identify endpoint.
Changelog: create entries from changelog.csv.
Help center: create categories and articles from kb_articles.csv.

See API overview and the full reference at /api/v1/docs on your workspace. AI tools connected through the MCP Server can also create articles and changelog entries.

Support conversations

Conversations can't be created through the API, so conversations.jsonl can't be imported. Keep it as an archive. You can create tickets in the new workspace through the tickets API if you need open issues to carry over.

Step 5: Check and switch over

Compare post counts and spot-check a few posts, statuses, and vote counts.
Update links in your app and website, and reinstall the widget with the new workspace's address.
Tell users where the new portal is. See Migrate from another tool for announcement and redirect tips.