Older guides for AEF, Vanilla, PunBB, FluxBB, Beehive, TangoBB and Unclassified NewsBoard described installer packages from earlier generations. Those steps have been consolidated here so you can evaluate a maintained destination and preserve the community data that matters.
IN THIS ARTICLE
01 Plan and perform the migration
- Inventory members, groups, private forums, topics, posts, attachments, avatars, bans and custom extensions. Record board permissions and important discussion URLs.
- Make a complete database and file backup, preserve its encoding, and verify a separate restore. Keep the source forum available while you test a migration in a restricted destination.
- Choose a supported target forum and examine its official importer or conversion documentation for your exact source version. Do not assume password hashes, private messages or attachments are supported by every converter.
- Run a trial conversion on copies. Compare member and post counts, sampled older discussions, private forum visibility, character encoding and attachment downloads.
- Plan a posting freeze for the final conversion, repeat the verified process with current data, map important URLs and monitor notifications after reopening.
02 Verify the complete result
Use ordinary member and moderator accounts to test permissions. A conversion that preserves every post but exposes a private board is not complete. Decide explicitly how password resets, unsupported data and inactive accounts will be handled.
03 Resolve an unsupported migration path
Do not assume changing the PHP version upgrades the forum software. If there is no trustworthy conversion tool, use a documented export or a carefully reviewed data migration, and retain a protected read-only archive where appropriate.
04 Example: record evidence from a forum trial conversion
| Sample | Compare before and after | Launch requirement |
|---|---|---|
| An old topic with attachments | Author, date, text, formatting and downloaded files. | Required content remains readable and correctly attributed. |
| A private staff discussion | Guest, ordinary-member and moderator access. | Private content and direct attachment links retain intended access controls. |
| A returning member | Account mapping and supported sign-in or reset workflow. | The member can recover access without exposing old password data. |
| A bookmarked public discussion URL | Its mapped destination and HTTP behaviour. | The link reaches the equivalent discussion or an agreed useful archive. |
Record failures during the rehearsal and repeat the conversion after correcting the mapping. Matching total post counts alone cannot establish privacy, attachment integrity or account usability. Keep the source read-only until the agreed acceptance checks pass.
Common questions
Will every old feature transfer automatically?
No. Importers support particular source versions and data types. Identify unsupported fields, accounts and extensions before the final move and agree how each will be replaced or retained.
Can you help with the hosting side?
Request a migration review with the source application, size and required functions. Hosting migration and application conversion are different scopes; support can confirm the available service and any work that needs a developer.