Late last year we announced that Automattic had purchased Code Garage, and that the VaultPress team would be taking it over.  Since then, we’ve spent quite a bit of time and energy working on the next steps:  How do we merge the service Code Garage customers are used to with the VaultPress infrastructure?

Today we’re happy to announce a migration plan that provides Code Garage users with the protection they’re used to — while letting us improve security and backup services for everyone by focusing our resources on VaultPress. Through July 1, all Code Garage customers are invited to migrate to VaultPress.  To sweeten the deal, your first two months are on us — you won’t see a charge from Code Garage or VaultPress for two months after the migration.  After those 2 months, your Code Garage bill will remain  unchanged – you’ll keep paying what you’ve been paying as a Code Garage customer.

If you’re not interested in migrating, we’ll maintain your service at Code Garage through July 1, and give you your last month free.

Code Garage customers who decide to give VaultPress a try will get a VaultPress Lite plan with the addition of daily security scans. As a VaultPress customer, you’ll also have access to standard VaultPress services like automated restores, restore to alternate site, and the fantastic VaultPress support staff. To make sure nothing falls through the cracks, you’ll have access your original Code Garage backup snapshots for 30 days after migrating.

Best of all, the migration process is simple.  We’ve put together an automated migration tool to simplify the move from Code Garage to VaultPress:

This slideshow requires JavaScript.

To start the migration process, just head over to your Code Garage dashboard, where you’ll find instructions on how to proceed.

We’ve given this a lot of thought over the past few months, and I’m confident that this move will give current Code Garage customers — who I’ve grown quite attached to over the past 2 years — with the best possible service and technology moving forward.

For a little more info on how we got to this point, I’ve also published a post on CodeGarage.com — you can have a look here.

If you have any questions about how this will work, please contact us.