Skip to main content

Mage2Plenty v4.0 - We're now Byte8

· 3 min read
Byte8 Team
Byte8 Team
PlentyONE Connector Development Team

Mage2Plenty v4.0 completes our transition from SoftCommerce to Byte8. The PlentyONE connector you already rely on now lives under the Byte8 brand and infrastructure, with a leaner, consolidated module set behind the scenes — and a migration that's automated and thoroughly tested, not a weekend project.

We're now Byte8​

This release re-homes the connector under our new company, Byte8. It's the same product, same team, same roadmap — rebranded end to end:

  • PHP namespaces — SoftCommerce\* → Byte8\*
  • Composer packages — softcommerce/* → byte8/* (the suite is now byte8/magento-plentyone-suite)
  • Magento module names — SoftCommerce_* → Byte8_*
  • Profile database tables — softcommerce_profile_* → byte8_profile_*

Leaner, consolidated modules​

Alongside the rename, we merged the finer-grained modules into their parent modules. The result is fewer packages to install and track, and faster, more predictable upgrades — less footprint, less maintenance overhead, same functionality. For example, the standalone profile history, queue, schedule, and config modules now ship inside a single Byte8_Profile module, and the per-domain *Profile modules fold into their domain parents (Byte8_PlentyItem, Byte8_PlentyOrder, and so on).

Migrating is automated — and battle-tested​

The most important thing to know: your data is preserved. All plenty_* tables — items, orders, stock, customers, properties, categories, mappings, profiles, and settings — keep their exact names and contents. Only the seven softcommerce_profile_* tables are renamed, and that rename runs for you automatically during bin/magento setup:upgrade.

Behind the scenes, setup:upgrade runs Byte8 migration patches that:

  • rename the profile tables (FK-safe DDL);
  • re-point setup_module rows from SoftCommerce_* to Byte8_* (folding consolidated modules into their parents);
  • rewrite your configuration paths in core_config_data so settings are preserved;
  • migrate admin ACL resources so existing roles keep their permissions;
  • update stored source-model class references from SoftCommerce\… to Byte8\….

You don't run any SQL by hand. We validated the whole transition end to end on dedicated migration environments — clean installs and real upgrades from live SoftCommerce datasets — before shipping it.

No rush — a 3-month grace period​

Your existing installation keeps working. You can continue using your current package — softcommerce/mage2plenty-os (or softcommerce/mage2plenty-ac for Adobe Commerce) — and it will keep receiving releases for 3 months, until 14 September 2026. After that, switch to byte8/magento-plentyone-suite (-ac for Adobe Commerce) to keep getting updates. Migrate any time within that window.

Upgrade Guide​

Packages are now served from the Byte8 Composer registry. In short:

# Remove the SoftCommerce package (data stays in place)
composer remove softcommerce/mage2plenty-os --no-update

# Add the Byte8 registry and authenticate
composer config repositories.cargoman '{"type":"composer","url":"https://byte8.packages.cargoman.io"}'
composer config http-basic.byte8.packages.cargoman.io token YOUR_TOKEN

# Require the new package and upgrade
composer require byte8/magento-plentyone-suite ^4.0
bin/magento setup:upgrade
bin/magento setup:di:compile
bin/magento cache:flush

Adobe Commerce stores use byte8/magento-plentyone-suite-ac.

Read the full migration guide

Back up first and run it on staging. The step-by-step guide — including the complete table-rename and module-consolidation reference — is here: Migrating from SoftCommerce to Byte8.

Resources​

Questions about the upgrade? Reach out to us at support@byte8.io.