How to Migrate from Upvoty to Feedbackly
Move selected Upvoty requests to Feedbackly with a CSV export, field mapping, and a reviewed pilot. Check what happens to votes, comments, identities, and statuses.
By Feedbackly · Updated
Product walkthrough
Watch request collection, voting, and status communication in the product walkthrough.
Watch the product walkthroughSee what the destination board provides
Practical context for How to Migrate from Upvoty to Feedbackly
To migrate selected Upvoty requests to Feedbackly, export your source data, prepare title and description columns, and test a small reviewed import during board creation. This transfers request text. It does not restore the complete history of votes, comments, identities, attachments, or roadmap statuses.
Confirm the destination fits before preparing the file. Feedbackly boards are public and managed by one account owner. If your current process depends on private boards, shared administration, or a custom domain, resolve that requirement first. The migration is a workflow choice as well as a data preparation task.
Save the source history and select the requests to move
Upvoty documents CSV exports for posts, voters, comments, and activity, including filtered exports. Save the relevant files and record the board, filters, and export date. Check the downloaded records rather than treating the appearance of a file as proof that the desired backlog is complete.
Choose the requests that are still relevant and suitable for a public board. Keep completed or obsolete items in the archive when moving them would create confusion. Retain source IDs in an internal migration log so you can answer questions about the old board without publishing voter or customer details.
Source: Upvoty: Data exports
- +Keep the original files separate from the cleaned import copy.
- +Record which requests were deliberately excluded and why.
- +Preserve comments and voting history in an appropriate archive.
Prepare a two-column CSV and preview it
Map the selected request name to title and the public problem description to description. Remove unrelated columns from the import copy instead of relying on the destination to interpret source-specific fields. Use double quotes around fields containing commas or line breaks, and double any quotation marks inside a quoted field.
The fictional CSV below illustrates the format. In Feedbackly board setup, choose CSV, paste the text, and preview the requests. The preview accepts up to 100 requests, a title of at most 120 characters, and a description of at most 5,000 characters. Edit and deselect records before confirming publication.
title,description "Schedule weekly reports","Administrators manually send the same report each Monday." "Save report filters","Analysts need to reuse a date range and segment without rebuilding the view."
- +Use explicit title and description headers.
- +Check that formatting and the original customer problem survived parsing.
- +Keep confidential evidence outside the public description.
Verify the new board before changing customer links
Compare every pilot request with its selected source record. Confirm titles, descriptions, and the intended public audience. Imported requests start under review with zero votes; previous votes, author identities, comments, attachments, and statuses are not recreated automatically. Keep any source history your team still needs in the archive.
Invite a small group to find a request, vote, add a comment, and understand a status update. Record old-to-new links in your migration log and explain where historical information remains available. Change the feedback link in your product only after the pilot passes your acceptance checks. Retain the original source while resolving any mismatch.
- +Verify that an old completed item has not become a misleading new promise.
- +Test the participation path with an appropriate customer account.
- +Assign an owner for the link change and later migration questions.
Keep exploring this topic
These next reads help you move from the concept on this page to a framework, tool, template, or deeper comparison you can apply right away.
Questions teams usually ask
Is there a native Upvoty migration connector?
This guide uses a prepared CSV import. Feedbackly does not provide a native connector that restores the full Upvoty board history.
Will Upvoty votes transfer?
No. Imported requests start with zero votes. Retain the exported voting records separately if you need historical evidence, and explain the reset when introducing the new board.
Can I preserve my private board or custom domain?
Feedbackly does not currently support private boards or custom domains. If either is required, evaluate a destination that supports it before switching.
Test selected Upvoty requests in a new board
Start a seven-day Feedbackly trial and preview a small CSV import. Review the resulting requests and publication model before moving your customer feedback link.