How Painful Is it to update from 2.2.6 to 2.3.1 or higher?

[ericbailey6052]

Hello, I know enough to be dangerous when it comes to backend development of Magento 2.  We currently run version 2.2.6 and I am interested in using some 3rd party analytics tools, such as hotjar.  Hotjar states it requires 2.3.1 or higher or else it will break the checkout page, my backend development team states that updating would be "a huge project that would break our custom functionality" I feel like they are blowing smoke and just lazy.  Is it truly that painful to go up a few versions?  Any insight would be much appreciated.  Thank you!

[novamulleraef4]

At first glance,THCA Flower Prerolls and traditional joints might look the same. But once you dig a little deeper, you’ll see that the source, legal status, and activation process are what set them apart.

Both can offer an amazing smoking experience. It just comes down to what’s legal where you live, what shopping options you have, and what kind of vibe you're looking for.

Whichever option you choose, make sure you from reputable sellers, start slow if you're new, and enjoy responsibly. Happy smoking!

[fahiyovuti399a]

Upgrading from Magento 2.2.6 to 2.3.1+ can definitely be more involved than it sounds, especially if your store has a lot of custom modules, theme overrides, or third-party extensions. The jump from 2.2.x to 2.3.x introduced significant framework changes (like Elasticsearch replacing MySQL for catalog search, GraphQL APIs, and new PHP requirements), so it’s not just a patch — it’s a minor version upgrade that can affect compatibility. Your dev team is right that it can break custom functionality if those modules aren’t updated for 2.3.x, but it’s also not an impossible task. With a proper staging environment, full extension audit, and step-by-step testing, the process is manageable. The “pain” level depends on how much of your current setup deviates from Magento core. If you need Hotjar and other modern integrations, it’s worth doing the upgrade — just make sure you budget time for debugging and QA rather than expecting it to be a quick push to production.

[stellaalon13ed]

Upgrading from 2.2.6 to 2.3.x isn’t just a small step — it brings core changes (PHP requirements, database updates, GraphQL, etc.), so custom code and extensions need testing and possible refactoring. Your team is right that it’s not trivial, but it’s definitely doable with proper staging and planning. If you need 2.3.1 for Hotjar, I’d suggest treating it as a proper upgrade project rather than a quick patch.