Structure
Categories, forums, subforums, ordering, descriptions, and supported permissions.
Available migration objects and capabilities depend on the selected source and target systems. Check current integration status before using this planning guide.
What the migration covers
The plan identifies public and private entities, ownership, moderation state, permissions, files, and destination constraints before loading records.
Discussions
Topics, posts, replies, timestamps, edits, status, moderation, and relationships.
Community
Users, profiles, roles, groups, authorship, and supported reputation data.
Private data
Attachments, inline assets, private forums, and messages when approved and portable.
What requires separate scope
Themes, plugins, badges, custom reputation algorithms, authentication integrations, search indexes, and platform-specific moderation workflows are reviewed separately.
How the workflow works
- 1. Inventory: Count public and private entities, users, roles, files, relationships, and source identifiers.
- 2. Map: Define destination categories, permissions, user resolution, topic state, and unsupported fields.
- 3. Pilot: Transfer representative forums including long topics, attachments, edits, and edge cases.
- 4. Reconcile: Compare totals and validate authorship, chronology, nesting, files, links, and permissions.
- 5. Cut over: Coordinate read-only mode, final delta, indexing, and post-launch exception handling.