If you're moving to AnnounceKit from another changelog tool, you don't have to start from a blank feed. AnnounceKit's Migration tool can import your existing posts so your release history stays intact.
What you can import
AnnounceKit currently supports importing posts from these sources:
Headway
Beamer
GitHub (release notes from a public repository)
Noticeable
Note: the ReleaseNotes.io importer has been discontinued and is no longer supported. If you're migrating from ReleaseNotes.io, reach out to support and we'll help you bring your posts over manually.
How to run a migration
In the dashboard, open Settings > Migration.
Pick the platform you want to migrate from.
Enter the public URL of your existing changelog — or, for Beamer, your App ID (see the per-source formats below).
Start the import and wait for it to finish — the importer pulls each post and creates a corresponding draft post in your AnnounceKit project.
Review the imported posts before publishing them.
Per-source formats
What you need to enter depends on the source:
Source | What to enter |
Headway |
|
Beamer | Your Beamer App ID (not a URL). You can find it in your Beamer dashboard or in your Beamer embed code as |
GitHub |
|
Noticeable | Your public Noticeable newsfeed URL (for example |
What gets imported
For each source, the importer reads the publicly visible content and creates an AnnounceKit post for each entry. As a rule of thumb you can expect the following to come across:
Title of each post.
Body / description text. Basic formatting (paragraphs, lists, links) is preserved where possible.
Publish date from the source, when available.
Known limitations
Because the importer is reading public pages rather than connecting to private APIs on each platform, a few things do not migrate automatically:
Comments and reactions from the original platform are not imported.
Subscribers and email lists are not imported. You'll need to invite users to subscribe again from AnnounceKit.
Categories, labels, and tags may not map 1:1 onto AnnounceKit's Labels. Plan to recreate the labels you care about and re-tag posts after import.
Embedded images and media hosted on the source platform may need to be re-uploaded if they're served from URLs that expire or require authentication.
Private or unlisted posts on the source platform aren't visible to the importer and won't be migrated. Make the relevant posts public first, or recreate them manually.
Targeted / segmented posts are imported as standard public posts. Re-apply segmentation rules in AnnounceKit afterwards if you need targeting.
After the import — what to verify
Imported posts arrive as drafts. Before publishing, take a few minutes to:
Open a few posts at random and confirm titles, bodies, and dates look right.
Check images and links render correctly. Re-upload any image that didn't come through.
Recreate labels in Labels and apply them to the imported posts as needed.
Decide what to publish. You can publish posts in bulk, keep older ones as drafts for archival, or delete entries you don't want public.
Set up redirects on your old changelog (if you control it) so existing links land on your new AnnounceKit feed.
Troubleshooting
The import returns no posts. Make sure the URL you pasted is the public changelog URL (not a dashboard or admin URL), and that the changelog is reachable without logging in.
Some posts are missing. Posts that were private, draft, or hidden on the source platform won't be visible to the importer. Make them public on the source first, then re-run the import.
Formatting looks off. Heavy custom HTML on the source can render differently in AnnounceKit. Edit the imported post and clean up any leftover markup.
You don't see your platform listed. If you're moving from a tool not listed above (including ReleaseNotes.io, whose importer has been discontinued), reach out to support — we can usually help you get your existing posts into AnnounceKit by exporting from the source and importing manually.
Need a hand with your migration? Drop us a message in the chat and we'll walk through it with you.