Transitioning to a Relational Database

Imagine you're part of a team at a burgeoning social network startup. With a surge in user growth and the need for enhanced analytics, coupled with rising complaints about data inconsistencies, the company has opted to transition from a document-based database to a relational database. Currently, the application includes these features: - User Authentication - Friend Connections - User Interactions (such as likes) In the existing document database, data is stored in a denormalized format, as seen in the User entity example: { 'userID':1, 'firstName': 'John', 'lastName': 'Doe', 'friendsID': [2, 3, 4, 5], 'postsID': [4, 12, 9, 10], 'interaction': [{'type': 'like', 'id': 44}] } What steps would you take to manage this migration project effectively?