Migrating from Magento Go to Magento Community

You’ve probably already heard the news about Magento Go closing down. Anyone wishing to sign up to the service is now greeted by a shutdown notice. The offical date that the platform will be closed down is 1st February 2015.

So, what next?

As mentioned in the article above, BigCommerce has signed a deal with eBay to move all existing Magento Go clients across to their platform. However, that’s not the only option for customers. A lot of solution providers are trying to tempt customers to their platform, however, Magento itself has two offerings: Magento Community and Magento Enterprise.

The beauty of Go

The simplicity of the Magento Go platform (its lack of customisability) means that for the majority of clients, migration will be fairly straightforward, however, it’s going to be interesting to see exactly what this process will entail and how smoothly it will be for clients of BigCommerce.

Migrating to Magento CE

For clients looking to stay on the Magento platform, and are also looking for power and flexibility, you might be tempted by Magento Community – and rightly so!

There are a number of things to remember when you’re looking to move your site from Go to Community, some of which can get quite technical and that’s why working closely with a company such as Branded3 means that we can take the headache out of the transition.

Here’s an overview of differences between Go and Community:

Support from Magento

Magento Community: No direct support from Magento, but a good partner will always be available for support.

Magento Go: Phone, Mail, Live support

Optimised, tuned hosting

Magento Community: No hosting is supplied, but working with a partner overcomes this

Magento Go: Hosting is built into the Go platform

PCI Compliance

Magento Community: There is no payment bridge with Community

Magento Go: Built into the hosted solution

Gift Cards

Magento Community: There is no default functionality within Community

Magento Go: Built into the hosted solution

Store Credits

Magento Community: There is no default functionality within Community

Magento Go: Built into the hosted solution

Theme / Layout Editor

Magento Community: There is no default editor within Community, however, you have access to the code-base and can make bigger and better changes!

Magento Go: Built into the hosted solution from the admin system

New themes and Extensions

Magento Community: Offers the flexibilty to use pre-built themes or add code to new ones. Has a vast array of community plugins (both free and paid for) to add more scalability to your solution. You can edit theme and core files directly if required.

Magento Go: Only pre-determined themes and extensions could be used, and these were very limited. Limited JS Support. No access to code.

From this listing, you should be able to see the value that was being received from customers on the Go platform, but it should also show the flexibility of the Community platform – anything Go did, Community can do and it can definitely do a lot more as well. It’s fast, scalable and secure.

Whilst this shows how the platforms differ, of course, migrating your content and domain name are also big parts of the process of migration. Migrating between Magento versions means that you won’t lose any content due to the data being re-mapped. All of the fields available can be set up within Community.

If you’d like to discuss how Branded3 can smooth your tranisition from Magento Go to Magento Community, then please get in touch.

By Douglas Radburn. at 11:16AM on Tuesday, 08 Jul 2014

Doug is our Senior Open Source Web Developer since bringing his knowledge and skills to Branded3 in 2009. A founding developer of our Twitition and Competwition platforms, Doug has also been lead in our Open Source Projects on Magento ecommerce solutions and Wordpress CMS platforms. Follow Douglas Radburn on Twitter.

comments

Leave a Reply