E-commerce SEO
Affordable SEO services for small business: 5 best proven
Affordable SEO is a scoping decision, not a shopping decision. This guide shows what a small budget actually buys, what to buy…
Web development · Magento & BigCommerce
Magento development and BigCommerce support, or a planned way out.
We work on Magento and BigCommerce stores, and we are honest about how: our Magento development is mostly maintenance, security patches, upgrades and fixes on existing stores, and our BigCommerce work is theme, app and integration fixes. We don’t build large new Magento stores. When the upkeep of either platform costs more than it returns, we plan and run the migration to Shopify or WooCommerce, with rankings protected.
200+ clients served 500+ projects delivered
Free Magento development audit, no obligation. Your store URL is all we need to start.
Free Magento audit
We’ll check your Magento or BigCommerce store and send a PDF report within 2 workdays.
Three fields and you’re done. The PDF report shows what we found on your own pages and accounts, and the order we’d fix it in. It covers the problems we see most often:
- Unsupported versions
- Patches nobody applies
- Extension conflicts
Chat on WhatsApp
Questions about Magento development first? Send us your URL on WhatsApp.
Your PDF report comes by email. If you want to discuss going ahead after reading it, we’ll set up a video meeting. We use your details only for this audit.
Fit
Who it’s for
- Magento 2 and Adobe Commerce stores that need patches, an upgrade or someone to keep them running
- Stores still on Magento 1, or on a 2.4 release whose support has ended, that need a plan
- BigCommerce stores that need Stencil theme changes, app clean-ups or integration fixes
- Owners weighing an upgrade against a migration and wanting the numbers on both
Not the right fit for large new Magento builds or complex multi-site Adobe Commerce programmes with their own agency teams. For those, a specialist Magento agency is the better choice.
Problems we fix
Where Magento and BigCommerce stores get stuck.
- 01
Unsupported versions
A Magento 2.4 release past its support dates, without security fixes, on PHP versions nearing end of life.
- 02
Patches nobody applies
Security patches postponed because the last update broke an extension.
- 03
Extension conflicts
Dozens of extensions overriding the same parts of Magento, so every change has side effects.
- 04
Expensive hosting
Servers sized for Magento’s demands, costing more each year as the store stands still.
- 05
BigCommerce theme edits lost
Changes made in a theme copy that can no longer take theme updates.
- 06
No exit plan
A store that should move, but nobody has mapped the URLs, data and integrations to do it safely.
In 1:10 · animated
Before we change anything, we check five things.
A short animated walk-through of the first checks in our audit. No sound needed: everything is on screen, and the transcript is below.
What we check first in a Magento or BigCommerce store, an animated explainer of 1:10 with on-screen captions and controls to pause.
Read the transcript
- What we check first in a Magento or BigCommerce store Five checks, from the version you run to the way out.
- 1. Is the version still supported? Adobe publishes support end dates for each Magento 2.4 release. Past them, no security fixes arrive. (Example store. Source: Adobe Commerce lifecycle policy.)
- 2. How far behind are the patches? Security patches get postponed because the last update broke an extension. (Example store.)
- 3. Which extensions fight each other? We list every extension that overrides the same core class, because those break together. (Example store with 48 extensions.)
- 4. What does hosting cost per order? Servers sized for Magento cost more each year while order volume stays flat. (Example store.)
- 5. Is there a plan to stay or move? If moving is right, we map URLs, data and integrations first, so search traffic and orders survive.
- Then we fix them, in that order. Want this checked on your store? The free growth audit covers all five, in writing.
Our approach
Magento development and BigCommerce support in four paths.
Path one of our Magento development is keeping a store safe. Adobe’s lifecycle policy gives each Adobe Commerce 2.4 release three years of standard support from its release date, and some releases a year of extended support. The dates matter: on Adobe’s table, extended support for 2.4.4 ended on April 14, 2026 and for 2.4.5 on August 11, 2026, and 2.4.6’s standard support ended on August 11, 2026. We check your exact version against that table, apply security patches on a staging copy, test checkout and key extensions, then patch the live store.
Path two is upgrading Magento or Adobe Commerce when it’s worth it. An upgrade within the 2.4 line usually means updating extensions, checking custom code and moving to a PHP version the new release supports. PHP’s supported versions page shows PHP 8.2 getting security fixes only until December 31, 2026, so the server is part of the plan. We list every extension and customization, estimate the work and compare it with the cost of a migration before you decide.
Path three is BigCommerce development and support. BigCommerce stores run on Stencil, its Handlebars-based theme engine, or headless on Catalyst, BigCommerce’s storefront framework built with Next.js and its GraphQL Storefront API. We make Stencil theme changes with the Stencil CLI in a way that survives theme updates, clean up apps that overlap, and fix integrations. Catalyst storefronts are covered through our Next.js development work.
Path four is moving away. When a Magento store costs more in hosting, patching and developer time than it earns from the flexibility, or a BigCommerce store needs features or apps it can’t get, we plan the migration, whether it is a Magento migration or a BigCommerce move: products, customers, orders and content moved, every URL mapped and redirected, tracking rebuilt. Most stores move to Shopify through our Shopify migration service; stores with deep WordPress content may be better on WooCommerce.
We are honest about depth in Magento development and BigCommerce development. Kashif has worked on Magento and BigCommerce stores, but these platforms are a smaller part of our work than Shopify and WordPress. That’s why we focus on maintenance, upgrades and migrations, where a developer background and careful testing matter most, and don’t take on large new Magento builds.
In Magento development, every change is tested on staging first. Magento changes are made on a copy of the store with the same extensions, checked through product pages, cart, checkout and the admin, then deployed in a maintenance window you approve. BigCommerce theme changes are previewed before they are applied. A rollback plan is ready before anything touches the live store.
Tracking and SEO are checked after every change, because upgrades and theme changes are a common reason purchase tracking stops and pages drop out of the index. We compare analytics purchases with store orders, check Search Console, and fix what moved. That ties into our technical SEO work for stores.
The decision to stay or start a Magento migration is made on your numbers. We add up the yearly cost of staying, including hosting, patches, extension licences and developer time, and compare it with the one-off cost of a migration and the running cost of the new platform. Some stores should stay and upgrade; others save money within a year by moving. You get the comparison in writing.
How we use AI here
Where AI helps on Magento and BigCommerce (and where it doesn’t).
Extension audits
Dozens of extensions and overrides mapped and explained quickly before an upgrade.
Migration mapping
Products, attributes and URLs matched between platforms faster, then checked by a person.
Upgrade notes
Release notes and patch lists summarized so testing focuses on what changed.
Where it doesn’t: AI tools never get database access or customer data, and patches, upgrades and data moves are carried out and checked by a developer, step by step, on staging first.
What’s included
What our Magento and BigCommerce work covers.
Version and support check
Your exact release checked against Adobe’s support dates and PHP support.
Security patches
Applied on staging, tested through checkout, then applied live.
Upgrades
Extensions, custom code and server checked, upgrade planned and carried out.
Extension clean-up
Overlapping or abandoned extensions removed or replaced.
BigCommerce theme work
Stencil theme changes made to survive updates; Catalyst through Next.js.
App and integration fixes
Overlapping apps cleaned up and broken integrations repaired.
Stay-or-move comparison
The yearly cost of staying compared with migrating, in writing.
Migration away
Products, customers, orders and content moved, URLs redirected, tracking rebuilt.
How we run it
Four steps, in this order.
Version check first, because support dates set the urgency. Typical timing for Magento development: the scope within 2 workdays, the build in 2 to 4 weeks depending on size, then testing, launch and handover in the final week.
Step 1
Check
Magento or Adobe Commerce version, support dates, PHP, extensions or apps, hosting and tracking reviewed.
Step 2
Choose the path
Patch, upgrade, support or migrate, recommended from the numbers.
Step 3
Do the work
On staging first, tested through checkout, with a rollback plan.
Step 4
Verify
Orders, tracking and Search Console checked after every change.
Pricing
Starting prices, in US dollars.
The audit is free. Paid Magento development work starts at these prices, and your exact cost is fixed in writing before any work begins.
-
Free Magento audit
Free no obligation
We’ll check your Magento or BigCommerce store and send a PDF report within 2 workdays.
Get my free audit -
After the audit
Magento or BigCommerce project
From $1,200 one-off, fixed scope
Fixes, upgrades or a migration plan, built and tested.
- Version and support check
- Security patches
- Upgrades
- Extension clean-up
-
Monthly maintenance
From $200 monthly
Patches, updates and fixes.
- A version and support report with a recommended path
- Patches, upgrades or fixes tested on staging, released with your approval
- For migrations
All prices are starting prices in US dollars. Custom work beyond these options is quoted after the audit.
Per project or monthly
What you get
- A version and support report with a recommended path
- Patches, upgrades or fixes tested on staging, released with your approval
- For migrations: data and URL maps, redirects and post-launch checks
- Updates by email and WhatsApp, and a video call when you want one
Pricing
How pricing works
We quote after a short audit, once we’ve seen the account or the store, so the number is based on the real work. Each project is a fixed one-off cost, agreed before work starts: from $1,200. Ongoing patching can move to a monthly plan.
Start with the free audit to get a quote for your store.
Sources
The documentation we work from.
Platform rules change. These are the official pages we check the work against, so you can check it too.
- Adobe Commerce lifecycle policy: support dates by release
- PHP supported versions: PHP
- Stencil overview: BigCommerce
- Catalyst: BigCommerce’s headless storefront framework
- Migrate to Shopify: Shopify Help Center
- Site moves with URL changes: Google Search Central
FAQ
Straight answers.
Can’t find yours? Ask on WhatsApp or by email and we’ll answer it.
Do you build new Magento stores?
No large new builds. Our Magento development is maintenance, security patches, upgrades, fixes and migrations away. For a large new Adobe Commerce build, a specialist agency is the better fit.
Is our Magento version still supported?
Check Adobe’s lifecycle table for your exact release. For example, extended support for 2.4.4 ended in April 2026 and for 2.4.5 in August 2026. We check yours as the first step.
Should we upgrade Magento or move to Shopify?
It depends on what the flexibility earns you against the yearly cost of hosting, patches, extensions and developers. We compare both on your numbers and recommend one.
Do you work on BigCommerce?
Yes: Stencil theme changes, app clean-ups, integration fixes and migrations. Headless Catalyst storefronts are built in Next.js, which we also work in.
Will we lose rankings if we migrate?
A migration always carries some risk, but mapping every old URL to its new page with 301 redirects, as Google recommends, protects most rankings and links.
What happens to our orders and customers in a migration?
Products, customers and order history are moved with the platform’s import tools or migration apps, and checked against the old store before launch.
Can you take over a Magento store from another agency?
Yes. We start with an audit of the version, extensions, custom code, hosting and tracking, then fix the riskiest problems first.
How do you use AI on Magento work?
AI tools help map extensions, summarize release notes and match data between platforms; a developer carries out and checks every change on staging.
Related guides
Read before you decide.
E-commerce SEO
Email marketing cost: 5 best proven price drivers
Email marketing cost is five bills in one: the tool, the list, the sends, the flows and the people. This guide prices…
E-commerce SEO
PPC pricing: 7 best proven budget tips
PPC pricing has two parts: money paid to the platform for clicks, and money paid to the person or agency managing the…
Free growth audit
Find out what’s holding your store back.
Tell us about your store. We’ll review your tracking, campaigns and SEO and send you a written audit with the top fixes, ranked by impact.
- Written audit as a PDF, delivered within 2 workdays (see a sample)
- A video meeting to go through it, if you want to discuss next steps
- Free and no obligation
- Read-only access or screenshots are enough