Adobe CommercetoMagento Open Source
Move from Adobe Commerce to Magento Open Source, with every row accounted for.
Same release, same catalogue, same customers and orders. We rehearse the conversion on a copy of your store, prove the result table by table, and give you the evidence before anything changes on your live site.
Fixed fee, from £999 + VAT
| Table | Expected | Actual | Result |
|---|---|---|---|
sales_order | 234,235 | 234,235 | Match |
customer_entity | 61,902 | 61,902 | Match |
catalog_product_entity | 18,440 | 18,440 | Match |
cms_page | 212 | 212 | Match |
Why merchants move to Open Source
Adobe Commerce is a strong fit for businesses that use its full feature set. For many merchants, the edition renewal is the moment to ask whether the store still relies on B2B, content staging, gift cards or customer segments. When it doesn't, Magento Open Source runs the same platform without an edition licence to renew, and converting keeps your code, your data and your Magento release.
-
Same platform
Magento Open Source is the same codebase your store already runs on, without the Commerce-only modules.
-
Same release
We don't bundle in a version upgrade. 2.4.7-p6 Commerce becomes 2.4.7-p6 Open Source, so the change is limited to the edition.
-
Only what you use
Our audit shows exactly which Commerce-only features your store depends on, so you can see what you would give up before you decide.
-
Budget where it counts
Without an edition licence, your platform costs come down to hosting, development and support: lines you choose and can plan for. What you spent on the edition can go into performance, features or growth.
-
Your team keeps working
Developers, extensions built for Open Source, hosting knowledge and admin habits all carry over.
A careful conversion, by design
An edition change touches most of your database. We treat it as a controlled change with evidence at every step, not a script run and a hope.
-
We never work on your live store
Everything happens on a restored copy of your database and code. Our tooling never connects to a production system. The only thing that reaches your live store is a script you have reviewed.
-
Nothing is removed without a tested archive
Anything the conversion drops is archived first, and every archive is restored into a scratch database and checked before we rely on it.
-
Every row is accounted for
Each row of your data ends up preserved, transformed, archived, deliberately discarded or regenerated. Nothing changes silently.
-
Encrypted settings checked before and after
Payment gateway keys and other encrypted settings that decrypt before the conversion are proved to decrypt after it.
-
You review everything before it runs
The live conversion is a commented script with a reviewer's guide. We can run it for you, or your team or host can, under your own change process.
-
We prove the live result
After go-live we compare your converted live database against the copy we verified in rehearsal. We sign off only when they match.
The process
Six stages. Most conversions take one to two weeks from audit to go-live, depending on your extensions and data.
-
Audit Typically 2–3 days
You send a database dump and a copy of your code. We check whether the store can be converted, list what depends on Commerce-only features, value anything that won't carry over, and report on your extensions. You get a clear go or no-go before any conversion work starts.
-
Decisions With you
We agree what happens to Commerce-only data such as store credit and gift card balances, which extensions need replacing, and when the cutover window will be.
-
Rehearsal
We convert the copy, verify it and repeat until it passes cleanly. Your code moves to Open Source at the same release, and the converted store is booted and checked page by page.
-
Sign-off
You receive the conversion report, with every figure shown as expected against actual. You test the rehearsed store and place a test order yourself.
-
Cutover A planned maintenance window
A backup is taken and proved to restore, then the reviewed script is run and the converted code deployed. We can do this for you, or your team or host can. There is no window where both editions work at once, so the store is in maintenance for the duration.
-
Proof
We check the live result against the rehearsed conversion and resolve any difference we can't account for before we close the project.
What changes, and what stays the same
Stays the same
| Your store | After conversion |
|---|---|
| Products, categories and attributes | Same |
| Customers and addresses | Same |
| Orders, invoices, shipments and credit memos | Same |
| CMS pages and blocks | Same |
| Store configuration and payment credentials | Same |
| URLs and redirects | Same |
| Your Magento release | Same |
| Your media files | Not touched |
Changes
-
Content staging and scheduled updates
Open Source has no staging, so each product, category, page or rule keeps the version that is live at the cutoff. Other versions are archived.
-
Store credit, gift cards and reward points
No Open Source equivalent. We value the balances and export them so you can decide how to honour them.
-
Returns (RMA), customer segments and B2B
No Open Source equivalent. Data is exported and archived. If you rely on these we'll discuss replacements at audit.
-
Commerce-dependent extensions
We identify them at audit. Replacing or adapting them is quoted separately.
Is my store suitable?
Outside these? Talk to us. The audit will tell you either way.
- Magento 2.4.4 to 2.4.8
- MySQL 8.0, MySQL 8.4, or MariaDB 10.4, 10.6 or 11.4
- A single database (split checkout or sales databases will need a custom quote post-audit)
- Adobe Commerce on your own hosting or on Adobe Commerce Cloud, which we'll confirm at audit. Leaving Adobe Commerce Cloud also means moving to new hosting, which we can plan with you.
Pricing
From£999 + VAT
A fixed fee for a standard Adobe Commerce store with no custom data migration, agreed after the audit. No day rates and no open-ended estimates.
Audit only: £399 + VAT. The audit is charged whatever the outcome. If it's a no-go, the report is yours and you can come back to us when the store is ready.
Included
- Read-only audit and go/no-go report
- Rehearsed conversion on a copy, repeated until it verifies
- Code converted to Magento Open Source at your current release
- Conversion report for sign-off
- Reviewed, commented live conversion script and reviewer's guide
- Verification of the live result against the rehearsal
Priced separately, only if you need them
- Replacing or adapting Commerce-dependent extensions
- Replacing Commerce-only features such as gift cards or B2B
- Moving hosting, including off Adobe Commerce Cloud. We can recommend a hosting partner we have worked with for many years.
The final fee depends on the size of your database, the number of extensions and any custom data migration, such as moving reward points to another platform. You'll have it in writing before any conversion work begins.
Questions
Will my store be offline?
Yes, for a planned maintenance window. Open Source code cannot run against a Commerce database, so there is no point where both work. We rehearse the cutover so you know how long it takes before you book it.
Do you need access to our live server?
Only if you want us to run the cutover. We work from a database dump and a copy of your code, and our tooling never connects to your live server. The live conversion is a script you have reviewed: we can run it with access you grant for the cutover, or your team or host can run it.
Can we go back afterwards?
Before go-live, yes: your original database is never changed. After go-live, orders and customers written to the new database would be lost by going back, so we prove everything before that point.
Are you upgrading our Magento version at the same time?
No. The release stays exactly the same, which keeps the change small and testable. We can quote an upgrade as a separate project afterwards.
What happens to reward points and gift card balances?
By default we value the balances and export them, so you can decide how to honour them. If you want them carried over to another rewards or gift card solution, we do that through an extension that you own. It is quoted separately as custom data migration.
What about our customer data?
Copies are held securely, used only for the conversion, and deleted when the project closes. Personal data is anonymised before anything is shared beyond the engineers doing the work. We sign an NDA on request.
Why a fixed fee?
Our process is the same on every project and the audit tells us the size of the job before we quote, so we can price it up front.
Can you support post-conversion?
Yes, we can talk about it. Once your store is running on Magento Open Source, we're happy to open a conversation about picking up its ongoing support.
Request an audit
Tell us your Magento version, roughly how many products and orders you have, and where you're hosted. We'll reply within one working day with next steps.