Moving Drupal 7 Website to Drupal 9 Multisite for Online Content Publisher

The knowledge hub was initially powered by Drupal 7. But, the Drupal 7 website had every topic (MicroLED, OLED, Graphene, etc.) clustered together. So, the client wanted to create individual subsites for OLED, MicroLED, e-paper, Graphene, etc., within a multisite. He felt creating a multisite network would make things more organized and help him serve a larger market. Also, a multisite comprising a number of subsites is cost-effective to maintain as well.

So, he sought to work with a partner with a thorough knowledge of Drupal 9 multisite network. This was when he found Capital Numbers’ work portfolio, liked it and approached us for a tie-up.

He wanted us to migrate existing data from Drupal 7 to Drupal 9. It was incredibly complex because we needed to move hundreds of existing files and images. We didn’t want to move everything in one shot. We aimed to migrate content and configurations individually.

While moving all the data, we also had to:

• Evaluate the current site’s security
• Analyze the migration’s impact on the site’s design
• Evaluate modules that would work on Drupal 9

In short, the leap from Drupal 7 to Drupal 9 wasn’t a simple update. We had to build a new site on Drupal 9 with empty subsites and then import all data from Drupal 7 to 9 using custom commands.

Capital Numbers had handled migration work in the past. But, every project entails varying degrees of challenges. We had to be proficient with custom migration commands for this one.

We started by chalking out a migration plan. As per this plan, we decided to take care of the following:

• Perform an audit of the Drupal 7 codebase
• Execute the migration process with custom commands
• Test everything end to end
• Go for rollbacks if issues arise
• Release to production

Step by step, we went ahead according to this plan. We began by auditing the Drupal 7 site and found we needed to remove several deprecated codes. We also did a full content audit so as not to migrate unwanted data.

After the analysis, we installed the Drupal 9 multisite. We then created seven exact replicas of the existing Drupal 7 site within the multisite. We kept the Drupal core files the same for all the subsites. But, we kept the database tables separate for each.

After creating the replicas, we performed migrations to move all data and logic to their corresponding counterparts in Drupal 9. We ran the Drush command to handle several custom migrations at this stage.

We used CSS to take care of specific UI elements. We upgraded to the CKEditor 5 from CKEditor 4 to make web page texts customizable. We also made several banners and social media components more configurable. We stored all the data using MySQL DB solution, which offers excellent scalability and protection.

After migration, we conducted a thorough QC of the configurations, code, logic, and designs. We found a few special characters popping up on the web pages. So, we ran custom scripts to remove all those. After ensuring zero errors, we deployed the multisite on Siteworks because Siteworks guarantees exceptional storage and uptime.

We collaborated with the client over Skype for the entire project and managed all tasks using Kanban boards on Teamwork. Kanban Boards helped us visually keep track of every progress area.

Our client sincerely appreciated our hard work on the project, which lasted 1.5 years. We successfully created a structurally enhanced multisite. It wasn’t easy to create a network of subsites within this multisite. But, because of our working knowledge of Drupal 9, we could do it well.

Here’s a lowdown of the project outcomes: