How should legacy content be handled during migration?

Starting with an empty Knowledge Base during migration emphasizes the importance of quality over quantity in knowledge management. This approach encourages organizations to reevaluate the information they have before migrating it to a new system. By beginning fresh, it allows teams to focus on creating high-quality, relevant content that meets the current needs of users.

This method can help eliminate outdated or ineffective information that might clutter a new system and lead to confusion or frustration for users looking for accurate and useful knowledge. It fosters a culture of continuously updating and refining content based on current best practices and user feedback, which is essential for effective knowledge management.

The other options may not align as well with the desired goal of ensuring a high-quality, relevant Knowledge Base. Keeping and updating legacy content might perpetuate outdated practices, while archiving for reference could lead to a reliance on old information that isn't actively used or relevant. Reformatting existing content does not address whether that content is still accurate or valuable, and it might just reproduce old information in a new format without any real improvement or reassessment.