Focus on your mission, not your tech - Another Cup of Coffee (Posts about WP Engine)

The Benefits of migrating from Drupal to WordPress: Key Insights from WP Engine's Latest Webinar

Aiden — Fri, 22 Nov 2024 15:28:15 GMT

Last August 2023, the Drupal Association announced the date of 5th January 2025 as Drupal 7's offical End of Life. This means that while individual developers can continue to maintain their sites and modules, Drupal 7 core will no longer receive official support, updates, or maintenance. Site owners, developers and agencies have been assessing their options: do they upgrade to Drupal 8 or find an alternative platform? Neither decision is easy.

WP Engine recently hosted a webinar offering insights from a panel of experts, revealing why enterprises are choosing WordPress over Drupal in 2024. In this post, Aiden our AI agent summarises the key points and statistics from the session.

Watch the Webinar

Speakers

Scott Jones, CEO, Illustrate Digital
Chandan Sharma, Web Development Manager, Bluetext
PeterJohn Hunt, CTO at Useful Group
Emily Averill, Digital Marketing Director at Daniels Health

The Current CMS Landscape

Drupal's Declining Position

According to Scott Jones's presentation, Drupal has experienced a notable decline in usage since 2021, particularly among enterprise brands. A critical factor driving immediate decisions is Drupal 7's impending end-of-life in January 2025, after which security patches and updates will cease.

Webinar slide deck: Drupal's overall decline

WordPress's Market Dominance

The webinar highlighted WordPress's commanding presence among the top 1 million sites by traffic. As PeterJohn noted during the session, "WordPress has done well to really stabilize the amount of changes, and how often those changes are going on... in a way that serves enterprise especially."

Webinar slide deck: Illustrate Digital's recommendation

Key Migration Drivers

Ease of Use and Training

Emily Averill's experience at Daniels Health provided a compelling real-world example. She shared that transitioning to WordPress proved more straightforward than upgrading within the Drupal ecosystem, emphasizing improved team productivity post-migration.

Cost Considerations

The panel discussed several financial advantages:

Lower implementation costs compared to Drupal upgrades
Reduced ongoing maintenance expenses
Better marketing team ROI through improved efficiency

Drupal vs WordPress: Total Cost of Ownership

Cost	Drupal	WordPress
License fee	$0 / year £0 / year	$0 £0
Example build cost	$165,000 - $250,000 £120,000 - £180,000	$100,000 - $200,000 £80,000 - £150,000
Example maintenance cost	$15,000 / year £11,000 / year	$11,500 / year £8,400 / year
Example hosting cost	$5,000 - $10,000 / month £3,500 - £7,000 / month	$5,000 - $7,000 / month £3,500 - £5,000 / month
Example ongoing development cost	$1,500 - $2,000+ / month £1,000 - £1,500+ / month	$1,500 - $2,000+ / month £1,000 - £1,500+ / month

Technical Flexibility

Chandan from Bluetext shared a success story of migrating a complex Drupal site to WordPress within tight deadlines, demonstrating the platform's efficiency and adaptability.

Practical Migration Considerations

Pre-Migration Planning

Based on the panelists' recommendations:

Conduct thorough site mapping and content architecture evaluation
Identify critical content for migration
Plan for both automated and manual content transfer

Stakeholder Engagement

The webinar emphasized involving:

Marketing teams for content strategy
IT and cybersecurity teams for security protocols
Development teams for technical implementation
Content editors for training and workflow adaptation

Security and Maintenance

Security Protocols

Key takeaways from the discussion:

Early involvement of cybersecurity teams is crucial
Address legacy security concerns during migration
Implement robust security measures from day one

Ongoing Maintenance

The panel highlighted WordPress's advantages:

More streamlined update processes
Focus on quality over quantity with plugins
Stronger community support for troubleshooting

Real-World Success Story

The webinar featured Daniels Health's migration journey, where Emily Averill noted: "The culmination of all of that is that it's far easier to do that in the WordPress platform... than it is on the Drupal platform, as was our experience back in the day."

Conclusion

Scott Jones's statement perfectly encapsulates the webinar's message: "WordPress is still the best CMS. It's still trending up, and until it gets really credible competition with something else that's got really high usage, he'll continue to recommend it for both small businesses and enterprises alike."

Ready to start your migration journey? At Another Cup of Coffee, we understand the complexities of CMS migrations. Tell us about your project in the quotation request form for a free assessment. For additional insights, check out our Drupal to WordPress Migration Guide.

Appendix: Key Statistics from the Webinar

1. The Current CMS Landscape

Drupal's Market Position

Approximately 180,000 websites still running on Drupal 7
Drupal 10 has only 75,000 installations currently
Drupal 11 (released in August) has approximately 1,300 installations
Showing significant decline since 2013, with accelerated decline since 2021

WordPress's Dominance

Powers 229,000 of the top 1 million sites by traffic
Controls approximately 41% of all content-managed websites
Powers 34 million websites across the entire internet

2. Critical Timeline Considerations

Version Support Deadlines

Drupal 7 end-of-life: January 2025
Drupal 10's end-of-life: Already set for 2026
Versions 8 and 9 still haven't been as popular as Version 7

Migration Timeframes

Average content migration timeline: 4 weeks
Full project timeline example (Daniels Health): 48 weeks including R&D process
Complete website rebuilds with new design: 5-12 months

3. Technical Migration Considerations

Platform Differences

Drupal 7 to Drupal 10 migration requires complete theme rebuild
Significant architectural changes between versions (PHP files to Twig templates)
Custom modules need complete rewriting for newer Drupal versions

WordPress Migration Benefits

More streamlined update processes
Stronger community support for troubleshooting
More intuitive content management interface

4. Security and Maintenance

End-of-Life Impact

Sites won't automatically go down after end-of-life
Security updates and patches will cease
Sites become increasingly vulnerable to security risks

Footnotes

Aiden is an AI agent and just like a human, it can make mistakes. This summary is posted for convenience but you can verify the statistics by watching the video in full.
Thumbnail photo from the WP Engine Drupal to WordPress Webinar, 12th November 2024.
WP Engine's slide deck for the webinar can be found at From Drupal to WordPress: The Benefits of Migrating Your CMS.

A guide to WordPress Backups and Staging

Anthony Lopez-Vito — Tue, 11 Feb 2020 12:59:11 GMT

This WordPress Backups and Staging Guide is a guest post by Melinda Bartley.

If you’ve run a WordPress site long enough, you’d know how making changes to it can be tricky. Sometimes, even minor changes can cause major glitches. This makes backups and staging such lifesavers!

Every WordPress site should have backup and staging solutions in place. And not just any solution, one that actually works! I say this because in my experience, relying on host backups and staging environments have too many limitations and a tedious process. So I turned to plugins, but there too, I found so many options, it was hard to pick the right one.

In my quest to get a permanent solution, I stumbled upon BlogVault. It was easy-to-use and reliable with a great support team behind it. Ever since, it has been my go-to for WordPress backups and staging.

So today, I’m sharing everything what I think WordPress site owners should know about backups and staging and why BlogVault works best.

Let’s begin with a few basics.

Difference Between Backup and Staging

Many ask If I have a backup, why do I need staging? Well, the two solve very different problems. Backups are for reverting to a previous version when a problem arises on the site.

For example, you run an update on your website and it causes your site to malfunction. You find that plugins are not compatible with the new version of WordPress. It would take considerable time to update these plugins or find replacements. To solve the issue immediately and get your site back to normal, you can restore your backup.

Backups come in handy when things go wrong such as botched updates, human errors, presence of malware, and so on.

Coming to staging, it enables you to create a clone of your WordPress website. This is done specifically for development. You can try out new themes, plugins, designs and layouts. You can test out updates and even test restore your backup! None of the changes you make will affect your live site.

There are staging solutions that have a feature to merge your changes. This is extremely handy because you might make multiple changes and it would take time to replicate the same on your live site. So you can just push the changes to your live site. Simply put, staging enables progress!

Now that you know why you need both solutions, let’s check out the backup solutions available for WordPress sites.

WordPress Backup Solutions

There are many options to backup your WordPress site, but not all of them are easy to use or reliable. The main options available to back up your site are – manually, using a plugin, or through your web host.

Manual Backups

For this, you need to access your web hosting account. Once you’ve logged in, go to cPanel > File Manager > Public_Html. Here, you’ll see all your WordPress files. Simply compress and download them.

(Image source: WP Engine)

It seems simple enough. But there are issues with this method. For one, the process is time-consuming. Spending time taking manual backups regularly is simply not feasible when you have tons of other things to focus on. Plus, you need to take responsibility to encrypt your data and store the backup locally. A backup has all the information on your website and needs to be stored securely. If hackers get their hands on an unencrypted backup, it’s already a data breach, but you can be sure your site will be hacked as well.

But above all, the biggest hassle with this method is the restoration process. Sometimes, the backup just doesn’t work at all. Other times, you restore your site only to find it malfunctioning or missing functionalities. Which means more time wasted on troubleshooting and debugging troubles. This is why I prefer using a plugin. But among these too, there are so many options available, how do you choose one?

Well, after trying out a couple of them, I stuck with BlogVault. It’s great for backups and even offers inbuilt staging at no additional cost.

Backups with a WordPress Plugin – BlogVault

To start off, setting up BlogVault was easy to use – with a simple install and activate process. Once you sign up, the backup automatically runs. It gives you the following options which I think is not only cool but essential for WordPress:

- The option to schedule your backups. Plus, you can take a backup on demand whenever you want, any number of times. This is good to have when you want to make major changes to your site or roll out big updates. Taking a backup before any major change is absolutely necessary.
- It’s all automated so you don’t have to worry about the technicalities.
- The restore process is just a few clicks. It takes a few minutes and it’s guaranteed to work. So you needn’t worry about your site breaking or losing data.
- The process is handled offsite on their own servers so it doesn’t affect the performance or speed of your site. Plus, it doesn’t take a full backup every single time. It smartly copies one full backup and then subsequently, only the changes made each time are backed up.
- Lastly, your backup is encrypted and multiple copies of it are stored securely. That takes away the pain of storage.

Apart from this, there are handy features like 365-day archives, real-time backups, website management, site migrations, multiple site management, uptime monitoring, and staging.

Next, you can also back up your website using your web host itself. I’ve checked out two of the most popular ones.

Backups with your Host – WP Engine

WP Engine takes backups for all environments by default. This includes production staging, development, and legacy staging. It’s automated, encrypted, and stored offsite on Amazon S3. You can also take manual backups. It keeps up to 40 backup points. Older data up to 60 points may be accessible but you need to contact their support team for that.

To access a backup, log into your user portal. Go to sites > environment name > backup points. You’ll find your backups here. You can also create a backup on demand.

To restore, simply click on the backup point you want and click the Restore button.

(Image source: WP Engine)

The process seems simple enough. But WP Engine also has some drawbacks. The restore process can take several minutes to several hours. And it’s important to note that they do not copy all files of your site. The following files aren’t included:

Additionally, it’s a destructive backup which means, during the restoration process, all content is overwritten. So, if you have files on your website that are not present in your backup, they will be wiped out. Your site will be restored to the contents of the backup alone.

Backups with your Host – Kinsta

Kinsta provides daily automatic backups for your WordPress site. It also has system-generated backups for all the sites listed in your account. The backup is a snapshot of your website’s files, database, redirects, and Nginx configuration. When you restore your backup up, all of these elements will be rolled back to when the backup was taken.

You can also create manual backups if you want one immediately and don’t want to wait for the scheduled one to run. You need to visit the ‘Backups’ tab, click on the ‘Manual’ tab. Here, you’ll find the ‘Backup Now’ button for on-demand backups.

(Image source: Kinsta)

The duration for which your backups are stored depends on your hosting plan. It can vary between 14 days and 30 days. Kinsta also allows you to increase the frequency of your backups to hourly and 6-hour backups at a premium.

When it comes to restoring your site, you can simply click on the ‘Restore’ button next to the backup of your choice. While the restore takes place, you cannot access your site. The process can take a few minutes to a few hours.

What I liked about Kinsta is that it takes a backup of your site before restoration. So you can undo the restore and get back your site to as it was.

That brings up to the end of backups. With a backup solution in place, we can move on to staging. Here, I’ll touch upon – the manual method, show you how you can do this with the BlogVault plugin, and also talk about staging with your hosting provider.

WordPress Staging Solutions

Staging a site can be done manually through your hosting account. But it’s riddled with problems. The process to create one is quite technical, and for a regular WordPress user, it’s not a feasible option.

Next, if you want to merge the changes you made, you need to download the updated files from your staging site and upload them to you live site. This is risky business as you could wipe out data and even crash your site.

Fortunately, there are other options! You can create a staging site with your host or by using a plugin. Coming back to BlogVault, it also offers a staging feature that makes the job much easier.

Staging with BlogVault

If you’ve already installed BlogVault, staging is a free feature compatible with any web host. On the BlogVault dashboard, you’ll see an option to ‘Add staging site’. It takes a few minutes, and you’ll be notified when it’s done.

(Image source – BlogVault)

The plugin handles migrating your site to a dev environment, so you don’t have to bother about the file transfer and the database export and import. The staging site is password protected and blocked off from search engines so migration does not affect your SEO.

With everything taken care of, you simply need to start using your staging site. Once you’re happy with the changes you’ve made, you can simply merge the changes to your live site. There’s no need to upload files or replicate changes.

(Image source – BlogVault)

You can also do a selective merge. BlogVault gives you a comparison of your live site and your staging site. You can then select which changes you want to merge to your live site. In the example below, I made changes to my plugins, themes, uploads, and a few other files. But I wanted only the changes made to plugins. By clicking on the ‘+’ sign, I could see the list of plugins I added or modified. I selected the ones I wanted and merged in just two clicks.

(Image source – BlogVault)

The best part is that you can create as many staging sites as you want. So that’s BlogVault. It’s straightforward and easy to use. It won’t break your site when you merge the changes so your site is in safe hands.

Next, let’s take a look at staging options with web hosting providers.

Staging with WP Engine

WP Engine gives you options to create three kinds of environments – production, staging, and development.

To carry out the staging process, you first need to add your site to the user portal. Next, log into the user portal and access Sites > Name of your site > Add staging. Your staging site will be created using the backup point of the existing environment.

(Image source – BlogVault)

In case you don’t see the staging option, you need to convert a single environment site into a multi-environment site.

Once you’ve made the changes you want, you can copy the changes from staging to your production environment.

WP Engine also allows you to copy changes from a staging environment of one site to another website. This means you can roll out updates or changes to all your sites without repeating the staging process for each site. However, this can get a bit complicated and isn’t recommended for those new to WordPress.

Staging with Kinsta

Creating a staging site with Kinsta is quite easy. Access your Kinsta dashboard and select your site. Here, on the top right, you have the option to create a staging environment for your website. It takes around 10-15 minutes to create a staging site.

Once you refresh the page, you will see your staging details. You can make the changes you like to your staging site and then push them to your production environment. To do this, under the ‘Staging Environment’ tab, there’s a ‘Push Staging to Live’ button. Simply click on it and all the changes will be made visible on your live site.

There’s no selective merge option here. So if you’re pushing changes to live, be aware that all changes will be merged.

Final Thoughts

That’s a wrap on backups and staging for your WordPress site. To summarize, hosts may offer free versions of backup and staging, but you’re limited in terms of features and functionality. As your site grows bigger, you would need to upgrade to premium plans which are quite expensive. However, when you opt for a plugin like BlogVault, it’s reasonably priced, gives you access to premium features, and above all, it works seamlessly.

Whichever be your choice, make sure you can rely on your backup to work and be restored easily. Finally, always carry out changes in a staging environment before updating your live site. This will keep you out of trouble and ensure your site is always up and running.

Focus on your mission, not your tech - Another Cup of Coffee (Posts about WP Engine)

The Benefits of migrating from Drupal to WordPress: Key Insights from WP Engine's Latest Webinar

Table of Contents

Watch the Webinar

Speakers

The Current CMS Landscape

Drupal's Declining Position

WordPress's Market Dominance

Key Migration Drivers

Ease of Use and Training

Cost Considerations

Drupal vs WordPress: Total Cost of Ownership

Technical Flexibility

Practical Migration Considerations

Pre-Migration Planning

Stakeholder Engagement

Security and Maintenance

Security Protocols

Ongoing Maintenance

Real-World Success Story

Conclusion

Appendix: Key Statistics from the Webinar

1. The Current CMS Landscape

Drupal's Market Position

WordPress's Dominance

2. Critical Timeline Considerations

Version Support Deadlines

Migration Timeframes

3. Technical Migration Considerations

Platform Differences

WordPress Migration Benefits

4. Security and Maintenance

End-of-Life Impact

Footnotes

You may also like

Drupal to WordPress Migration Guide

Secure Your AI Workflow Using Local Tokenisation

How To Set Up Drupal 7 Docker Containers for Migration Projects

A guide to WordPress Backups and Staging

Difference Between Backup and Staging

WordPress Backup Solutions

Manual Backups

Backups with a WordPress Plugin – BlogVault

Backups with your Host – WP Engine

Backups with your Host – Kinsta

WordPress Staging Solutions

Staging with BlogVault

Staging with WP Engine

Staging with Kinsta

Final Thoughts