Front-end Delivery Options
Magento Native Coupled Approach
Default and out of the box way of rendering content from Admin panel of Shopify. Popular as a quick straightforward way to start your own shop online. Entire further extensibility is based on 3rd party embeddable apps. Custom Themes or Custom Liquid Sections
Magento Headless Storefront
All data is fetched Magento backend and then online store is populated via combination of content coming from Magento and eventually other systems like PIM or CMS used by marketing department to build landing pages and marketing collateral offers best platform independency and reduce the vendor lock significantly
Where Merchants are migrating from Magento?
One of the most popular options for merchants to migrate from Magento is Shopify, right after it is WooCommerce and BigCommerce
Cost of license
There is open source license that cost nothing. And since Adobe acquired Magento it's now promoting switch to Cloud version of it branded as Adobe Commerce Cloud however deployment on premises is still possible.
Cost of license for Adobe Commerce on-prem and Cloud versions is dependent on GMV.
Adobe Commerce / Magento Commerce on-prem license cost is lower than Cloud version.
| Gross Merchandise Value (GMV) | Magento Commerce On Premise | Magento Commerce Cloud |
|---|---|---|
| $0 – $1M | $22,000 | $40,000 |
| $1M – $5M | $32,000 | $55,000 |
| $5M – $10M | $49,000 | $80,000 |
| $10M – $25M | $75,000 | $120,000 |
| $25M+ | $125,000 | $190,000 |
B2B Capabilities
Magento add-on B2B module allows to customize it's functionality for use cases beneficial for manufacturers, distributors and wholesalers.
What are main B2B Features each business-to-business store should provide?
- Request for Quote
- Tiered Pricing
- Matrix Ordering
Where Magento merchants are migrating their stores?
Two main platforms where merchants that used Magento previously are switching to are - Shopify and BigCommerce
Migration from Magento - main steps
- Theme Migration - dependent on what would be the destination platform tech stack theme migration would require fetching all custom templates as HTML and then porting those to Liquid (in case of Shopify) or Stencil (in case of Bigcommerce) usually each theme would contain following custom templates:
- Main Page
- Collection Page
- Product Details Page + custom templates for PDP's
- Blog post
- Landing Page - DNS and Redirects Audit - were A/B tests setup on this store? what with redirects?
- Extensions Audit - what plugins are used currently and what replacement plugins should be picked on the destination platform
- Search, filtering and faceted search - does destination platform offers same capabilities or 3rd party solution like Algolia would be required?
- Custom Code and features audit - throughout lifetime of the magento store since it's self-hosted open source solution multiple workarounds and custom coded features are developed both on the customer facing front-end as well as on the Admin side. You will need to review also all Workflows or custom backend automations.
- Data migration - historical orders of customers, customers accounts, product details pages, landing pages, blog posts, redirects
- Email templates and transactional emails migration
