J2Store 3 to J2Commerce 6

Free

$0.00

Build Your New Joomla 6 Store. Your Data Is Already Inside It.

J2Commerce 6 and J2Store 3 cannot share a site, so your old store stays online and keeps taking orders while you build the new one. The adapter reads your users, articles, categories, products and orders into a fresh Joomla 6 site. You spend your time on the design, and when you are ready to switch, you click Resync to bring over the latest orders and customers.

A Fresh Site, Filled With Your Existing Store

Starting over on Joomla 6 is the easy part when the data is already there. Here is what the adapter copies for you, in an order that keeps every record connected.

Old Store Keeps Selling

The adapter only reads from your old database and never changes it. Your Joomla 3 store keeps working and taking orders for as long as you need it, and you switch when the new site is ready.

Your Server or a Remote One

Connect to the old database in the same database as the new site, in a different MySQL or MariaDB server, or through an SSH tunnel when the host only allows that. Add SSL and a CA file to verify the server certificate.

Sections That Unlock in Order

A tile stays locked until the tiles it depends on are synced, so orders cannot arrive before the products and customers they refer to. You follow the board instead of working out the sequence yourself.

Customers Keep Their Accounts

Shopper accounts move with their group membership, and passwords are copied as they are stored whenever the stored hash is one PHP can still verify. Those customers log in with what they already use, and no one has to register again.

Articles, Menus and Modules

Every product is a Joomla article, so the articles come too. Menu links are rewritten to the migrated pages, and modules whose extension is installed on the new site keep their menu assignments.

Category Picker With Preview

Per category, create an identical one, map onto one you already built on the new site, or skip it. Preview shows the result before anything is written.

Products, Variants and Stock

SKUs, per-variant stock, weight and dimensions, tiered prices by user group, option choices and inventory quantities all move over, so you do not re-key a catalog.

Images Converted to WebP

Product images are converted and resized into main, thumbnail and tiny versions. You choose the folder and the quality.

Orders With Every Record

Address snapshots, line items, option choices, status history, fees, taxes, discounts, deliveries and downloads all stay attached to their order.

Tax and Delivery Setup

Tax profiles, rates, rules and geo zones, plus flat-rate and table-rate delivery, so checkout prices match what you charged before.

Old URLs Keep Working

URL and alias maps from sh404SEF and Joomla core redirects become Joomla redirects, so ranked pages and bookmarks still reach the right product.

Resync Before You Switch

One click per tile pulls the orders, customers, products and articles that arrived after your first copy. Verify Resync then checks counts, links and financial totals.

Spend the Project on the Design, Not the Data

Moving a store off Joomla 3 usually means converting database tables by hand, and that is the part nobody wants to pay for. The adapter does that work. You get a fresh Joomla 6 site where you choose the template and the look, and your users, articles, categories, products and orders are already in it.

Build and test the new design against your real catalog
Nothing on the old site is rebuilt, re-keyed or exported to a spreadsheet
Rehearse on a staging copy first, then repeat on the live site

The Old Site Keeps Taking Orders While You Build

J2Commerce 6 and J2Store 3 cannot live on the same site, so the adapter connects to a separate database, on your own server or a remote one, and only reads from it. Your Joomla 3 store stays live and unchanged, and customers keep placing orders while you work on the new one.

The old database is only read, never written to
Works with a database on your server or a remote one
Go live on the day you choose

Click Resync, Then Switch

When the new site is ready, open the Resync section in the migrator and click the tiles for Users, Articles, Products, Customers and Orders. Each pass inserts new rows and updates changed ones, so the orders and customers that arrived during your build are in the new store. Resync sends no customer emails, and order status history is added to, never replaced.

Verify Resync checks counts, links and financial totals
Choose which source categories to pull articles from
Retry, Resume and an exportable log for every run

Order History and Customer Accounts Arrive Complete

Each order arrives with the address snapshots from the day of purchase and every record attached to it. Customer accounts come with their group membership, and passwords are copied as stored when the hash is one PHP can still verify, so those customers log in the way they always have. When a customer asks about a purchase from years ago, you open the same details you had on the old store.

Line items, option choices and status history
Fees, taxes, discounts and deliveries per order
Saved billing and delivery addresses arrive with their owners

Real-World Use Cases

Dana sells printed apparel: 600 products with color and size variants and around 4,000 orders. Her host is dropping its old PHP versions, and she assumed a new Joomla 6 site meant rebuilding the catalog by hand. She installs a clean Joomla 6 site, installs the adapter, connects to the old database and runs the sections in order. Then she picks a template and spends her weeks on the look of the shop, with her products and order history already in place. Her old store keeps selling the whole time.

A food seller takes orders every day and cannot close the shop for a migration. They run the full migration once while the old store keeps selling, then spend a few weeks on the new design. On cutover weekend they run Resync Users, Resync Products, Resync Customers and Resync Orders, then Verify Resync, and read the row counts and financial totals against the old store. The orders taken during the build are in the new store, and no customer receives an email about them.

An agency inherits a J2Store 3 store whose database answers only through an SSH tunnel. The client does not see why the move matters and wants to keep the cost low. The agency turns on SSH Tunnel Mode in the Migrator Options and connects with Mode C, so the quoted hours go to the redesign and not to converting data. The category picker maps the old categories onto the agreed structure, menus come across with rewritten links, and the Redirects tile runs before go-live so the client's old links keep working.

A membership seller bills subscriptions through one gateway and runs a third-party plugin with its own tables. They install the Subscription Product plugin, check how many subscriptions exist, map the gateway to an installed J2Commerce payment plugin and migrate. They detect the custom tables, choose Import for each, and use the Plugin List to see which payment and app plugins to install next.

Keep Selling on the Old Store, Switch When the New One Is Ready

The J2Store 3 Migrator is a separate download that requires J2Commerce Migrator 6.2.6 or later, and Resync brings the latest orders and customers into the new site without changing your old one.

Translated In The Following Languages

Arabic Unitag (ar-AA), Chinese, Traditional (zh-TW), Danish (da-DK), Dutch (nl-NL), English (en-GB), English, USA (en-US), Finnish (fi-FI), French (fr-FR), German (de-DE), Greek (el-GR), Hebrew (he-IL), Italian (it-IT), Japanese (ja-JP), Norwegian Bokmål (nb-NO), Persian Farsi (fa-IR), Polish (pl-PL), Portuguese, Brazil (pt-BR), Portuguese, Portugal (pt-PT), Russian (ru-RU), Spanish (es-ES), Swedish (sv-SE), Turkish (tr-TR)