skip to Main Content
Imagewize Migration – WordPress Migration Case Study

We just finally did it. The Imagewize Migration is a fact! Imagewize has become IMWZ starting today. We have been thinking about a rebranding for quite some time, but we are finally taking steps. Today we migrated https://imagewize.com to https://imwz.io. And I must say it went pretty smoothly. Let us tell you how we did the WordPress Migration so you can learn from this.

Background

You must know that we moved to DreamPress, Managed WordPress hosting with Dreamhost. It is an amazing setup to run your WordPress business and I will highlight features ast the end of this post. There was one issue we bumped into as was due to WP Rocket DreamPress compatibility issues with DreamPress. This as the latter works with Varnish caching. So this is something you may no run into, but the rest is very similar to most WordPress migrations.

BackupBuddy Backup

We used BackupBuddy to backup the site and migrate it from the Dashboard to the new location. That saved us time using SFTP to SFTP everything to our local PC and then again to the new location. Both locations are in the US and from Bahrain using my meager Batelco ADSL here at Amwaj Islands would have been a massive PITA.

Wordfence Firewall Issues

We did run into one issue with Wordfence. We blogged about the fact that BackupBuddy and Wordfence do not like each other much before. It spoiled the database migration completely. As soon as the necessary files were unzipped we had a JSON error. One I could not just copy as it was in a BackupBuddy warning backup:

Error #839983: Failure parsing returned server data. SEe Status log for more details: `Unexpected token < in JSON at position 0`.
Resonse: `<br />
<b>Warning</b>: Unknown:Failed to open stream. Permission denied in
<b>Unknown<b/> on line <b>0</b><br />
<b>Fatal error</b>: Unknown: Failed opening required '/home/imgvps/imagewize.com/wordfence-waf.php'

There was an error because Wordfence was trying to load wordfence-waf.php from old server. Had to deactivate and remove Wordfence, empty cache before I could rename the file. Not sure if plugin removal was needed though, but did anyways. Just renaming wordfence-waf.php or .user.ini did not do the trick. Could have been a caching issue though. But hey, I would recommend removing Wordfence before you move. Or you will get stuck just like me.

301 Redirect from old to new domain

All our visitors and clients trying to reach us at the old website will be properly redirected to the new domain name. This we did with a fairly standard Apache redirect at the top of the .htaccess file:

#Options +FollowSymLinks
 RewriteEngine on
 RewriteRule ^(.*)$ https://.imwz.io/$1 [R=301,L]

As we only change the domain and not the permalinks the redirect RewriteRule was pretty straightforward. We will remove the site at the old domain as soon as we can. Will also allow us to reduce the VPS intake of RAM and save us some $.

 

Google Webmaster Tools Change of Address

You can also tell Google that you have moved. For the property that has changed address you can register just that. Click on the top right button to register the change.

Change of address

After that you can follow the steps below and:

  • pick the new domain,
  • confirm the 301 redirects properly
  • check that the verification code still works properly

Webmaster Tools Change of address Steps

Google Analytics Property & View Changes

Do not forget to update your Google Analytics property and view settings. These need to use the new url as well. Otherwise you will see a quick drop in traffic post domain name migration. We did it by going to the Google Analytics account in question. There under admin you can change the url for the property and for the view(s) you have.

property url

 

Google Analytics Filters Check

Please be certain to change your filters if you have additional views with filters like a valid hostname filter. Otherwise it will not register any visitors as it will not accept the new domain name. We now have:

imwz\.io|cdn\.imagewize\.com

but had the first filter hostname as imagewize.com and had not adjusted it right away. Fortunately we have multiple views so we still had data, but lost some for this spam free view. The second allowed host is for our CDN. We may adjust the name there, but we will keep it for now.

WP Rocket Compatibility

To make WP Rocket Cache work properly with DreamPress Varnish we did need to activate a separate plugin provided by WP Rocket. This plugin had to be added to

  • be able to empty Varnish cache on emptying cache using WP Rocket,
  • remove Varnish removal as an option as it is no longer needed,
  • ensure minification compatibility and
  • remove the HTML expires rules from .htaccess

DreamPress Goodies

The additional advantage we have now is that we were now part of a Dreamhost one-click installation. So we were able to move over to DreamPress. It is really amazing. It allows you to focus on your site and let them manage core updates, server updates. And this with a setup with one server for files, one for the database and one for Varnish caching.

Design Changes

We will be replacing the logo and favicon this week. Just some final tweaking to do so to speak. The weekend was good for a migration so we went for it. We promise you will see a new shiny logo and favicon soon. This besides the new icons for social media. The Facebook Page has been renamed already, but will get a facelift too as soon as the design part is done.

 

Advertisements

Jasper Frumau

Jasper has been working with web applications such as Joomla!, Magento and his favorite WordPress for more than a decade. He helps customers with webdesign and online marketing. Services provided are webdesign, ecommerce, SEO, content marketing. When Jasper is not coding, marketing a website, reading about the web or dreaming the internet of things he plays with his son, travels or run a few blocks.

Leave a Reply

Back To Top