Magento, kept healthy or moved off properly.
Adobe Commerce and Magento Open Source can model almost any catalog and any buying process. They also cost more to keep running than anything else on this list. We do the upgrades, the performance work and the integrations, and we will tell you when leaving is the better decision.
What Gigabit does on Adobe Commerce and Magento.
Gigabit maintains and extends Adobe Commerce and Magento Open Source stores: version upgrades and security patching, performance work, custom modules, front-end rebuilds, and integrations with ERP, product information and order-management systems.
We also migrate stores off Magento. A platform this capable is the right answer for a complex catalog with engineers behind it, and an expensive one for a store that no longer needs what it offers. Which of those you are is the first thing we work out.
The Adobe Commerce (Magento) work we take on.
Most Magento work is keeping a large system current. The rest is deciding what it should become.
Upgrades and security patching
Version upgrades along the 2.4 line with extension compatibility checked, custom code refactored where it blocks the upgrade, and a tested rollback. Regular support for 2.4.6 ended on 11 August 2026.
Performance
Full-page cache, Redis, search and indexer tuning, and profiling of the custom code that is usually the real cause of slow pages and slow admin.
Front-end rebuilds
Replacing an ageing Luma theme with a lighter front end such as Hyvä, or a headless storefront when the business case supports a separate codebase.
Custom modules
Modules written to Magento's extension points for pricing, inventory sources, B2B quoting and checkout, without editing core.
ERP, PIM and OMS integration
Catalog, price, stock and order flows between Magento and the systems of record, queued and reconciled so a failed message is found and replayed.
Migrations off Magento
A measured move to Shopify, BigCommerce or Adobe's cloud service: what must be rebuilt, what an app replaces, and what the business stops doing.
Adobe's AI is sold with the enterprise edition. The open-source store starts from nothing.
Which edition you run decides what you already have.
Built into the platform
Adobe Commerce customers get Adobe's AI-driven merchandising services. Magento Open Source does not include them.
- AI-driven site search and product recommendations as Adobe Commerce services.
- Generative tools for content and assets through Adobe's wider product family.
- Full REST and GraphQL coverage on both editions, so an agent can reach catalog, customer and order data.
Agents for a complex catalog
The stores that stay on Magento have complicated catalogs and complicated customers. That is where an agent saves real hours.
- Catalog enrichment across large configurable and bundled product sets, checked against rules before publish.
- A B2B service agent that answers from account-specific pricing, stock by source and order history.
- Order-exception triage between Magento and the ERP, with the correction prepared for a human to approve.
- Evaluation on your historical tickets and orders before launch, and monitoring afterwards.
Published prices, mapped to the job.
Every figure here is the same one on the pricing page. Nothing on this platform is quoted from a separate rate card.
A price marked “from” buys the base scope set out on the pricing page. Anything larger is quoted as a fixed price before work starts. Work with no natural end, such as ongoing development, is priced per engineer per month with no lock-in.
When Adobe Commerce (Magento) is the right call, and when it is not.
- The catalog is genuinely complex: configurable and bundled products, several inventory sources, many stores and currencies.
- B2B quoting, company accounts and negotiated pricing are central to how you sell.
- You have engineers, in house or retained, and the budget to keep the platform current.
- The catalog is simple and the checkout is standard. You are paying enterprise upkeep for a job a hosted platform does.
- Upgrades have been skipped for years because nobody can fund them. That gap only widens.
- You want new features to arrive without a development project each time.
Questions Adobe Commerce (Magento) teams ask
How much does Magento or Adobe Commerce development cost with Gigabit?
Upgrades, custom modules and performance work are staffed as an embedded pod at $3,000–$7,500 per engineer per month, with a two-to-four week trial and no lock-in. Migrations off Magento are fixed-price: Platform Migration starts at $7,000, and Magento sources are quoted above that base, up to about $40,000 for large multi-store catalogs. One scoped integration or workflow is $8,000 fixed over three weeks.
Should we migrate from Magento to Shopify?
Migrate if your catalog and checkout are simpler than the platform you are paying to maintain, or if upgrades keep being postponed. Stay if you depend on complex product types, several inventory sources or B2B quoting that a hosted platform would need custom apps to imitate. We scope both, and the answer comes from a list of what you actually use.
Can you take over a Magento store with a lot of custom code?
Yes. We start by mapping the custom modules and third-party extensions, what each does and which block an upgrade. Unsafe things are fixed first. We regularly take over systems other teams built.
Which Magento versions are still supported?
On Adobe's published schedule, checked in October 2026: regular support for 2.4.6 ended on 11 August 2026, with paid extended support to 31 August 2027. Regular support runs to 31 May 2027 for 2.4.7, 31 May 2028 for 2.4.8 and 31 May 2029 for 2.4.9. A store on 2.4.5 or earlier is out of support and should be upgraded or moved.
Do you work on Magento Open Source as well as Adobe Commerce?
Yes, both. The code base is largely shared. The difference that matters is what Adobe bundles with the paid edition, including B2B features and its AI-driven search and recommendation services.
Often scoped alongside.
Shopify
Builds, migrations, custom apps and Functions, plus support and returns agents grounded in live order data.
ShopifyBigCommerce
B2B and multi-storefront builds, headless storefronts, and the ERP integrations that make or break them.
BigCommerceOdoo
Implementation, custom modules, upgrades and store integrations from an Odoo Partner, plus agents on Odoo 20.
Odoo
Find out whether to stay or go.
Bring the version you are on and the list of what is custom. Thirty minutes for an honest read.