Magento 2 – Community Edition vs Enterprise Edition

When comparing two editions of any software package, the best way to come to a decision is by weighing the costs and benefits. While Magento EE does have some great additional functionality, if you're not using it then it may not worth it. Jake Smith is absolutely correct in mentioning the scope of Enterprise Edition support. It is limited to¹ :

• Magento installation and downloads
• Magento usage issues
• Basic configuration
• Troubleshooting, Bug Fixes (core only), and Escalation

Generally, you'll be using your in-house development team or a hired team, which would cover issues not covered by that scope:

• Code Development
• Development Support
• Optimization and Performance Tuning
• Custom Extensions
• Custom Interfaces
• Custom Configuration
• Core Product Upgrades
• Data Migration
• Best Practices Recommendations

This leaves you in a position to decide if you need the features available. Take into consideration these key features² :

• Customer segments
• Targeted promotions and merchandising
• Product suggestion tools
• Search with Solr
• RMA
• Customer rewards
• Private sales
• Automated email reminders
• Gift registry
• Gift cards
• Store credit

During the planning phase of your project, you'll need to think about how you will track the ROI for these features. Each feature will need to be thoroughly planned, implemented, and then reported against. You'll want to make sure that the money coming in more than covers the cost of the features. Also, you'll want to make sure that if you only plan to use a handful of these features that it wouldn't make more sense to have them developed or to purchase existing ones (use caution when purchasing third-party modules, but that's a different topic).

For some sites, Enterprise makes sense. There is a marketing team, internal or external that will help plan usage for the marketing suite. They might have a team in place to analyze usage and to constantly maintain these features. If not, then start with Community. We have large clients on both Community and Enterprise, and talk extensively before making a decision. As a trusted extension of our clients' companies, it is of utmost importance to put their needs first.

The biggest scare tactic that I've seen is that Community is "Not PCI compliant". This is a long-winded topic, and can be very complex. If you're doing the following, then you'll be ok:

• Filling out your PCI paperwork
• Implementing PCI policies
• Documenting your PCI technical policies (mostly for your host)
• Using a payment gateway that you redirect to (PayPal) or HTTPS to communicate with an API

You'll be ok. Once you start doing more than 20,000 transactions per year, there will be more paperwork - but this shouldn't scare you. Your provider will be happy to work with you to not only fill out the documentation, but answer any questions you may have (we also do this). If this is too vague or anyone would like to discuss, feel free to contact me. There is much more to it than this, but it's a great start. Basically, don't ever let anyone bully you into not using Community because it's "not for production use" or "only for development".

As far as I know, Magento does not go through PCI certification for Community Edition or Enterprise Edition. It is a long and expensive process. The only products available from Magento that are PCI compliant are:

• Magento Go
• Magento Payment Bridge

So, hopefully this is an alright guide to helping make a decision. Remember - if the features in Enterprise will pay off, then get it. It's a great product and has some really neat stuff. If not, then wait. Although it's a bit more involved to migrate from Community to Enterprise than starting on it, you'll save some money that you can use for an extra custom feature or better hosting.

Sources:

1. http://www.magentocommerce.com/support/ee/
2. http://www.magentocommerce.com/product/enterprise-features

Edit 3/10/14

Yanted has written a fabulous guide to this - some of the EE features in >= 1.13 actually make upgrades a little more painful than the below writeup would lead you to believe. As Marius points out in the comments that all passwords will have to be reset as encryption methods are handled differently between EE/CE.

See the blog for more details.

https://web.archive.org/web/20150208220803/ http://blog.yanted.com/2014/02/21/downgrading-magento-enterprise-to-community

Original post:

Migrating is actually very easy - point your CE codebase at your production database. There's little more to it than that (see below for some folder removal information).

If you're using a well-built EE-compatible theme it should be backward compatible.

Here are some little-known EE features you'll need to watch out for when downgrading to Community:

• No access to Customer Attributes from Admin Panel
• Customer segments will go away
• Catalog events, private sales, Invitations etc. will go away
• CMS hierarchies are not supported in CE
• Banners are not supported in CE
• RMA - people always seem to forget about RMA (information will be resident in db)
• Admin Logging information will be inaccessible (still resident in db)

If you have a large portion of your CMS built in EE I recommend you take a very thorough and methodical approach and make sure that your new CE theme (or backwardly-compatible EE theme) support the data that is still resident.

I also suggest not dropping any tables from the db prefixed with enterprise - as well as not removing any enterprise folders from your 3rd party themes. These are not considered as part of the EE install and you should take them along with you when you leave. You will need to remove the files and folders from the following locations:

• app/code/core/Enterprise
• app/design/frontend/enterprise
• app/design/adminhtml/default/default/layout/enterprise
• app/design/adminhtml/default/default/template/enterprise
• skin/adminhtml/default/enterprise
• skin/frontend/enterprise
• app/etc/modules/Enterprise_*.xml
• js/enterprise
• LICENSE_EE.txt
• LICENSE_EE.html

And of course, you need to consider the real biggie: Full Page Cache. I highly recommend that you find a decent 3rd party Full Page cache.

Best of luck!