Productboard Feedback

​

Step 1: Create a Slack App

1. Go to api.slack.com/apps
2. Click the “Create New App” button
3. Choose “From scratch”
4. Name your app (e.g., “Vistaly Migration App”) and select your workspace
5. Click “Create App”

​

Step 2: Configure User-Level Permissions

1. In the left sidebar, click on “OAuth & Permissions”
2. Scroll down to the “Scopes” section
3. Under “User Token Scopes” (not Bot Token Scopes), add the following permissions:
   • (to read messages from public channels)
   • (to read messages from private channels)
   • (to get channel information)
   • (to get private channel information)
   • (to get user information)
   • (to match users by email)

​

Step 3: Install the App to Your Workspace

1. Scroll up to the top of the “OAuth & Permissions” page
2. Click “Install to Your Workspace Name”
3. Review the permissions and click “Allow”
4. After installation, you’ll see a “User OAuth Token” that starts with
5. Copy this token and store it securely - this is what you’ll need for the migration

​

Step 4: Channel Access

​

Public Channels:

• The app can access the complete history of all public channels without being added to them
• This simplifies the migration process as no manual channel joining is required

​

Private Channels:

• The app will have access to private channels that the authorizing user has access to
• Private channels the authorizing user is not a member of will not be accessible
• Vistaly’s data migration tool will include a link to any instances it is unable to read so users can view those messages if they have access

​

Step 5: Export ProductBoard Feedback

1. Use ProductBoard’s export functionality to download your Notes
2. Save the exported file for the next step

​

Step 6: Share Required Files with Vistaly

1. Your Slack user token (starts with xoxp- or xoxb-) if using Slack
2. Your ProductBoard feedback export file

​

Step 7: Upload Vistaly Feedback

​

Important Security Notes

• The user token provides access to your Slack workspace data. Only share it through secure channels.
• User tokens have broader permissions than bot tokens and should be handled with extra care
• User tokens will expire if the authorizing user changes their password
• After migration is complete, you can revoke the token by:
  1. Going to api.slack.com/apps
  2. Selecting your migration app
  3. Going to “OAuth & Permissions”
  4. Clicking “Regenerate” or completely uninstalling the app

​

Data Migration Limitations

1. Private Channels: The app can only access private channels that the authorizing user is a member of
2. Direct Messages: The app cannot access direct messages (DMs) or multi-person direct messages (MPDMs)
3. File Access: While the app can see file metadata, downloading files may require additional permissions
4. Rate Limits: Slack API has rate limits that may affect migration speed for very large workspaces
5. Token Expiration: User tokens expire if the authorizing user changes their password

​

Need Help?