How to Migrate from Frill to Feedbackly

Keep an unchanged source copy and prepare a separate import copy. Frill lists CSV import/export on its pricing page; verify the available export and included fields in your own workspace or with Frill support. We have not verified a current dashboard export-menu sequence, so this guide does not prescribe one. Check that the file contains the intended ideas and note any filters or omissions.

If a developer prepares the records through Frill's documented Ideas API, its name, content, status, and created_at fields provide the source information to review. The API also describes votes, authors, and attachments, but their presence in a source record does not mean Feedbackly imports them. Convert rich content to a readable public description and retain the original separately.

Select only relevant requests whose descriptions can be public. Keep private notes, participant details, and internal evidence in your retained system. Record the source reference, intended destination, and exclusions in an internal log. That log lets the owner investigate an old request without putting customer history into the public description.

Source: Frill: Published export capability

Source: Frill: Ideas data fields

Use a header row with title, description, status, and created_at. Frill's idea name becomes the title; the cleaned explanation becomes the description. Keep titles between 3 and 120 characters and descriptions between 5 and 5,000. The dashboard importer accepts up to 100 requests and 100,000 characters per submission. Quote fields containing commas or line breaks and double quotation marks inside quoted fields.

Choose the status meaning before importing. Under review, pending, and open map to Under review; planned maps to Planned; in progress maps to In progress; completed, shipped, and done map to Completed. A source label such as 'Investigating' needs an explicit decision. Change it in the import copy or leave the status column unmapped to use Under review; an unknown mapped status is rejected rather than guessed.

Use a valid past ISO date, such as 2026-10-01 or 2026-10-01T12:00:00Z, for the original date. An unmapped date uses the import time. The fictional sample below is intended for the dashboard backlog importer. Board creation has a separate, simpler CSV preview that imports titles and descriptions with an initial Under review status; do not use that path when you need to retain mapped statuses and dates.

Create the destination board and open its dashboard. Expand 'Import a CSV backlog', paste the prepared CSV, and select 'Preview CSV'. Check the Title, Description, Status, and Original date mappings. Review each row and its error message; changing a mapping refreshes the preview, so recheck the selected rows before continuing. Duplicate rows are deselected by default, and matching existing requests are skipped when publishing.

Confirm that selected descriptions are safe to publish publicly, then publish only the accepted pilot rows. Inspect the resulting board and compare the status, original date, formatting, and count with your migration log. Imported requests have zero votes. Customer identities, historical votes, comments, attachments, and follower subscriptions do not transfer. Test a new submission, vote, comment, and owner status change with public-safe data.

Keep an old-to-new request reference in your internal log and explain the new destination with the launch announcement template. State which history remains available and how customers can ask about an earlier request. Change app and help-center links after the pilot passes, then assign one owner to check both destinations during the transition. Account cancellation and source deletion are separate decisions; an imported CSV alone does not establish that the old workflow is no longer needed.