There comes a time when your business needs to adapt and so does your website platform. Webdrips can manage the migration of your site on any version of Drupal to the latest Adobe AEM platform, and from the Adobe AEM 6.x platform to Drupal 7 or 8.
CMS migrations are usually complex endeavors, regardless if the migration is to Adobe Experience Manager (AEM) from Drupal or vice-versa. We feel that it's not just about moving content, which usually the more straightforward part. The real complexity is converting the site architecture, developing the functionality, and configuring the modules/components.
Drupal stores content and configuration in a database, whereas Adobe stores everything in files. Each CMS uses vastly different methods to define the architecture.
Because migrations are typically complex, we will sit down with your stakeholders and map out a process and timeline everyone's comfortable with.
Drupal 6/7 to Drupal 8 Migration
At Webdrips, we've handled complete website migrations, including HTML/CSS-based sites to Drupal, database-driven CMS-based sites to Drupal, Drupal to Drupal upgrades and migrations, WordPress to Drupal, and even Ubercart to Drupal Commerce shopping cart migrations. There are many ways to migrate a site, so let's sit down and figure out the best way for your website. For complex migrations, there's the Drupal Migrate Module, and for simpler migrations, the Drupal Feeds module may work just fine.
Migrating from Drupal 6/7 to Drupal 8 is significantly more straigforward. Drupal 8 has over 200 new features and improvements, including: extensive administrative tools, improved security, streamlined editing, enriched accessibility and much more. Regardless of which version of Drupal you're migrating from, Webdrips' team of engineers is here to help.
If you are currently running a Drupal 6 site, that version of Drupal is no longer supported, and your site is probably vulnerable to hackers. If you are not sure which version of Drupal you are currently running, please feel free to reach out to us.
For Drupal upgrades, we carefully scan all existing modules to both find out if they're being used, and determine if there's an upgrade path. Then we upgrade Drupal core, followed by one module at a time until the process is complete. The final step here is cleanup of any issues encountered during the upgrade, and in many cases re-applying some configuration that got lost in the process.
HTML/CSS to Drupal Migration
Converting from an HTML-based website to a Drupal CMS-based site is typically very straightforward, and involves the following process:
- Review your current site and map all the various content areas and sections into the field and entity equivalent in Drupal.
- (Optional) Identify a content tagging hierarchy so that tagging may be applied during migration, even if it's not immediately put to use.
- Identify all of your current dynamic content, and decide how to best convert it to follow Drupal best practices.
- Determine if there's any new functionality that may be added out of box or with minimal additional effort. For example, Drupal provides RSS feeds out-of-box.
- Next we'll find a base theme that most closely matches the current skin of your website, yet also will allow for future enhancements and compatibility with up-and-coming specifications like HTML5 and CSS3.
- Migrate the static content. This can be completely manual or completely automated, depending on the number of pages among other factors.
- Sign-off on the data model: are all the page types and fields in place and configured properly? Are images and files placed in the proper directory (folder) on the server? Does the content editor workflow meet expectations? Typically this is straightforward when converting an HTML-based sight to CMS because existing workflows and configurations were not in place to begin with.
- "Drupalize" the code for displaying existing dynamic content.
- Apply the theme (skin) to the static/dynamic content.
- Final signoff that static and dynamic content are displaying the same (or better) than the old site.
All of the other migrations discussed below include most/all of the above steps (except for Ubercart to Drupal Commerce migrations, but the overall concepts are the same).
Legacy CMS to Drupal CMS Migration
Get more flexibility and speed by migrating from Joomla, Magento, WordPress, or any other open source or proprietary CMS to Drupal. No matter what CMS you are migrating from, our knowledgeable team of Drupal professionals will find a customized solution to ensure a seamless and easy migration process.
The process for converting an existing CMS to Drupal is essentially the same as the HTML to Drupal covered above. However, an in-depth study of the PHP code to display static or dynamic content and pull in related content is required. In addition, recreating and improving the content adding/editing workflow is typically required, as content editors expect a new CMS to be as intuitive as the old one.
WordPress to Drupal Migration
This is another relatively painless migration with the aid of the Drupal WordPress Migrate module. We've used this module, and found the process relatively painless.
Legacy Database to Drupal Database Migration
If your legacy site stored content or user information in a database, that will typically need to be migrated to Drupal's database. Drupal includes a community-contributed module to aid in this task for many databases, which significantly improves the database to database migration.
Drupal Ubercart to Commerce Migration
Essentially what we're doing here is migrating a shopping cart from Ubercart to Drupal Commerce. It's not as painful a task as you might think, so please get in touch to learn more.
Drupal Migration Consulting
Our Drupal Migration Consulting specialists can carefully analyze your current website to uncover weak points, determine what version of Drupal to use (Drupal 7 or Drupal 8), and what modules need to be used, migrated or developed from scratch to get desired functionality.
Adobe AEM offers a very complete CMS platform. Because of that, migrations to AEM can be quite complex and there are a few methods of automating the migration process. First we'll sit down with you to develop a content migration workflow, and then we'll implement it with the following methodology:
Content Migration Flow
- Review existing content inventory, including content, metadata, images, design, active components, and so on for both desktop and mobile.
- Scrub and sanitize the existing content, remove broken links, identify missing media assets, etc.
- Organize the page hierarchy, menus, etc. to match the existing site. We want to make sure your URL structure remains consistent as much as possible and set up redirects otherwise.
- Decide if tools like the Digital Asset Management (DAM) make sense to further help your company tag, share, organize, and distribute media assets, reusable content, etc.
- Organize content hierarchy (which is different from your website hierarchy) according to AEM best practices. Here we consider how to best group pages by page type, the frequency of content updates, dependence between pages, etc.
After we've completed the above, upload the content to AEM can commence. Once we are ready for uploading content, there are tools our developers can use to help automate the migration process where possible. We will do a review and check to assure all content was migrated.