Moving a forum from one software package to another is a big job, but it is often the right call when the old system is abandoned, insecure or impossible to keep spam-free. Done carefully, members keep their accounts and posts, search engines follow the redirects, and the community barely notices anything except the improvements. This guide covers planning, test runs, passwords, redirects and launch day.
Decide whether migrating is worth it
Migration is worth the effort when one or more of these is true:
- The old software no longer receives security updates.
- It will not run on a PHP version your host still supports. See which PHP version your forum needs.
- Spam is out of control and the anti-spam tools are weak.
- You are paying a hosted community platform and want your data on your own server.
- Key features such as private messages, SEO-friendly URLs or backups are missing.
If the old software is still maintained and only needs updating, an upgrade is usually simpler; see how to upgrade forum software safely.
Take stock of what you have
Before choosing tools, list what must come across and what can be left behind:
| Data | Priority | Notes |
|---|---|---|
| Members, usergroups | Essential | Usernames, emails, join dates, post counts |
| Categories, forums, threads, posts | Essential | Including sticky and locked status |
| Attachments and avatars | High | Files plus the database records linking them to posts |
| Private messages | High | Members expect these to survive |
| Polls, reputation, signatures | Medium | Nice to keep, not always supported by importers |
| Custom profile fields, plugin data | Low | Often easier to recreate or drop |
Write down member counts, thread counts and post counts from the old forum. You will compare these after each test import.
Back up and freeze nothing yet
Take a full backup of the old forum's database and files (see forum backup and restore). Keep the old forum running while you test. You only close it on launch day, so members are not inconvenienced by weeks of preparation.
Run a test import
- Install the new software on a test subdomain with its own empty database. The shared hosting install guide covers this.
- Give the importer read access to a copy of the old database, not the live one.
- Run a dry run first if the importer supports it, so you can see what will happen without writing anything.
- Run the full test import and compare counts with your notes.
- Click through old and new versions of a few busy threads to check formatting, quotes, attachments and links.
Quick BB includes importers for existing forums and for CSV files, with a dry run, a progress display, ID mapping between old and new records, and resumable imports. Resumable imports matter on shared hosting, where a long-running request may be stopped by time limits; the import picks up where it left off instead of starting again.
Expect to repeat the test import a few times. Fix issues such as BBCode that does not convert cleanly, character encoding problems or usergroups that need mapping, then import again into a fresh database.
Handle passwords honestly
Forum software stores passwords as one-way hashes, and different products use different hashing methods. A good importer never tries to decrypt passwords. There are two safe approaches:
- Migrate the hash. Where the old hash format can be verified, the member logs in with their old password once and the new software re-hashes it in its own format.
- Ask for a reset. Where the format cannot be verified, members use the password reset to set a new password on first login.
The Quick BB importers never decrypt passwords; members either reset or migrate safely. Tell members in advance which approach applies, so a reset email does not look like phishing. Make sure email sending works first; see set up forum email with SMTP.
Plan redirects from old URLs
Years of search traffic and external links point at your old URLs. If they break, you lose that traffic. Search engine guidance for site moves recommends server-side permanent redirects (HTTP 301 or 308) from each old URL directly to its new equivalent, without chains, and keeping them for at least a year, ideally longer.
- Map old forum, thread and member URLs to the new ones using the ID mapping from the import.
- Redirect each old thread to its matching new thread, not to the home page.
- Test a sample of old URLs from your analytics or search console data after launch.
- Submit the new XML sitemap so search engines discover the new URLs quickly.
Quick BB uses friendly URLs such as /threads/125-how-to-install-php/ and redirects old ?f=, ?t= and ?u= style links. Check how your old forum's URLs are structured; links that use different patterns may need extra redirect rules in your server configuration. The SEO-friendly forum URLs guide and XML sitemap guide explain the rest.
Launch day
- Post an announcement a few days ahead with the date and expected downtime.
- Close the old forum so no new posts are made.
- Take a final backup of the old database.
- Run the final import into a clean database for the new software.
- Compare counts once more and spot-check content.
- Switch the domain or folder to the new software and enable your redirects.
- Open the new forum, post a welcome thread explaining what is new and how to log in.
After launch
For the first week, watch for login problems, broken images and 404 errors in your server logs. Keep the old database backup for months, in case you need to recover something the import missed. Pick a skin and settings that feel familiar so long-time members settle in; a classic layout and familiar skin colors help here. Ask members to report anything that looks wrong in a dedicated feedback thread, and reply to every report so people see the move is being looked after.
If you are changing hosting at the same time, do the moves separately where possible. Move the old forum to the new host first, then migrate software, so you only have one set of problems at a time. See how to move a forum to a new host.
Frequently asked questions
Will members keep their passwords after a migration?
Passwords should never be decrypted. Depending on the old format, members either log in once and have their password re-hashed, or set a new password with a reset.
How do I keep my search traffic after migrating?
Set up server-side permanent redirects from each old URL to its new equivalent, keep them for at least a year, and submit the new XML sitemap.
How long does a forum migration take?
Planning and test imports can take days or weeks, but the final switch is usually a few hours of downtime depending on forum size.
