Start with a small sample of your export. Check what it contains before choosing an import method. A total vote count, a list of voters and a comment thread are different kinds of data.
Use the checklist below for shared preparation and the final switch.
| Existing content | ProductLift destination |
|---|---|
| Requests or ideas | A feedback board |
| Planned work | A roadmap, with links to the requests behind it |
| Release announcements | A changelog |
| Help articles | A knowledge base |
| Customer details and revenue | Users and companies |
Create the boards you need first. Keep separate boards where they have different audiences or workflows. Use categories for topics within a shared board.
Use the source tool's current export options or API. Availability can depend on your plan and permissions. Keep an untouched copy of the export.
Check whether it includes:
If the source tool cannot export a field, ProductLift cannot recover it from a count or screenshot. Contact support with the source tool and a sample of its export to discuss a route. Do not email passwords or unrestricted API keys.
Use one row per post. Map the source fields to the post importer's supported columns. For example:
| Source meaning | Import field |
|---|---|
| Idea, card or issue title | Title |
| Description | Description |
| Workflow state or Trello list | Status |
| Product area | Category |
| Internal labels | Tags |
| Original creation date | Created Date |
| Due date | Estimated Date, if it represents expected delivery |
| Author's email | Author Email |
| Assigned teammate's email | Assigned To (Email) |
Do not map a due date to the creation date. Match assignees to existing ProductLift admins before importing.
Use Number of Votes for a total vote count. This does not identify the people behind those votes, connect them to revenue, or make them email followers.
If you have individual voter emails, group them by post and put a semicolon-separated list in Voter Emails. Check the preview and resulting voters. Keep author identity separate from voter identity.
For a source based on notes or insights rather than votes, such as a Productboard workflow, agree how to represent those records. Do not turn every note into a customer endorsement automatically. Preserve useful private context as internal notes or references, using a separate import/API step where needed.
Comments, relationships and attachments may need separate work through the API. A successful spreadsheet import does not establish that every part of the old workspace has moved.
For announcements, including a Beamer or Headway archive, use the changelog URL/feed importer when your source provides a compatible public feed or sitemap. Check its discovery preview for missing older entries.
For documentation, choose URL import or Markdown sync. Check images and links before retiring the source site.
Update your in-app links and widgets, reconnect SSO, and test with a customer account. Plan redirects for old public URLs where you control the hostname. A ProductLift redirect cannot change links served on a third party's domain.
Keep the original export until you have checked the imported content and customer access. Review notification settings before sending any announcement about the move.