Drupal is powerful and quick, making it an ideal choice if you’re considering upgrading your content management system (CMS) or eCommerce platform. It’s not quite magic, but it comes close.
We have migrated content and commerce platforms to Drupal for many clients over the years and we love the challenge! Whether it’s a straightforward migration or you want to enhance your offerings at the same time, we can work with you to make that happen.
We’ll also support you and your team in learning how to use Drupal. It’s not complicated, but we appreciate that moving to any new CMS can feel daunting. Importantly, we always consider staff as one of our ‘personas’ when we look at user experience for any new systems we build. Once you’re up and running, you’ll appreciate the difference that Drupal can make to getting the job done.
Our role in the history of Drupal migrations
Back in 2008, some of the current Full Fat Things developers worked at The Economist on a project to migrate to Drupal. We worked closely with Cyrve, a company that no longer exists but at the time had a huge impact on Drupal’s development. The Migrate module, created and used for that Economist migration, now forms part of the Drupal core and is the tool with which Drupal upgrades from Drupal 6 to Drupal 7, 8 and 9.
The Migrate module was built as a general purpose migration tool. It’s so powerful that it positions Drupal uniquely within the enterprise content management systems (CMS) space. It allows us to migrate, important and manage data in Drupal at scale and in a process-driven way that supports knowing full progress. There’s isn’t a single Full Fat Things project where the Migrate module isn’t involved, even if we aren’t upgrading from an older Drupal migration.
The Drupal.org website includes a case study on The Economist.com data migration to Drupal where you can read about our efforts and get a detailed insight. (You’ll also notice a lot of comments from Full Fat Things staff, if you know who we are!)
Since our time at The Economist, we’ve been involved in some large-scale sites that migrate, or import, large amounts of content and have huge numbers of users. These include data.gov.uk, which has mass public datasets of open data, and library sites for Wolters Kluwer and Croner-i that have millions of documents inside Drupal. Drupal implementations such as these don’t simply use the Migrate module for one-time migrations. Instead, they use Drupal Migrate to import content every day.