J2Commerce To EasyStore - Question | JoomShaper

Celebrate JoomShaper's Sweet 16 with Flat 35% OFF!

Claim 35% OFF
Back to the questions

J2Commerce To EasyStore

Stephane Hanrez

Stephane Hanrez

EasyStore 2 weeks ago

Hello,

I'm looking at potentially migrating my existing J2Commerce (ex J2Store) extension to EasyStore, but have some questions about it:

  • Can you confirm migration is possible from J2Commerce (evolution from J2Store) or is it purely restricted to olf J2Store ?
  • When using the migration mecanism, what part of the product data are migrated ? Are all product pictures correctly migrated to EasyStore products ?
  • Is EasyStore also using a Joomla article for each product, in the same way as J2Store, or is it using its own tables?
  • If using its own table, does it mean that I could potentially keep running both J2Store and EasyStores in parrallel (during the migration phase). Can I then delete all J2Store articles, or is that done automatically during the migration ?
  • Are emails templates from J2Store also migrated or do I need to recreate those ?

Thanks a lot for your answers.

0
5 Answers
Order by
Oldest Newest Votes
Atick Eashrak Shuvo
Atick Eashrak Shuvo
Accepted Answer
Support Agent 2 weeks ago #225047

Hello,

Thanks for your questions — here are the clarifications point by point:

Yes, migration is supported for J2Store / J2Commerce data, since it is based on the same core com_j2store structure. The migration tool is designed to work with that data model.

During migration, the tool typically transfers the main commercial data required by EasyStore, including:

  • Products (including core product information)
  • Categories
  • Orders (if included in your migration scope)
  • Customer-related data (depending on configuration)

Product images are migrated as well, provided they are stored in standard Joomla media locations or properly referenced within the J2Store/J2Commerce product structure. In most cases, image paths are preserved and reused in EasyStore.

EasyStore does not use Joomla articles for products. It uses its own database tables to manage all eCommerce data independently. This is different from J2Store’s article-based approach.

Because of this separation, you can technically run J2Store/J2Commerce and EasyStore in parallel during a migration phase. However, both systems will operate independently and will not sync data between them.

No data from J2Store is automatically deleted during migration — including products, articles, or media. Cleanup of legacy data must be done manually once you confirm everything has been fully migrated.

Email templates from J2Store are not migrated. These will need to be recreated and configured within EasyStore.

I

0
Stephane Hanrez
Stephane Hanrez
Accepted Answer
2 weeks ago #225138

Thanks a lot for this very good answer.

One additional question: Is it possible to migrate everything so I have data to work on my pages, templates, ... while I continue using J2Store in production, and once everything is ready, scratch the whole EasyStore DB and migrate again so I resync all data and can the move with EasyStore to production (PS: Even if I need to truncate a table in DB for this, that's not an issue) ?

Thanks

0
Atick Eashrak Shuvo
Atick Eashrak Shuvo
Accepted Answer
Support Agent 2 weeks ago #225141

Hello,

That approach is unfortunately not recommended with the current migration mechanism.

The J2Store → EasyStore migrator is designed as a one-time import process. Once data is migrated, the system does not track or re-sync previously imported records. Because of this, running the migration again on the same EasyStore database will not reliably overwrite or re-link existing entities (products, orders, relations, media references, etc.).

The main reason is that during migration, EasyStore generates its own internal IDs and relationships (product IDs, category mappings, order relations). These are not designed to be safely “re-mapped” on a second migration pass. As a result, repeating the process can lead to duplicated records, broken references, or inconsistent relational data.

For this reason, we do not support or recommend resetting/truncating the EasyStore database and re-running the migration as part of a staging-to-production workflow.

The recommended approach is to use a separate staging environment:

  • Set up a staging copy of your Joomla site
  • Perform the full migration there once
  • Complete all configuration, design, and template work in EasyStore
  • Keep J2Store running on production until final cutover
  • When ready, perform a single final migration to production

This ensures data integrity and avoids any risk of duplication or inconsistency.

0
Stephane Hanrez
Stephane Hanrez
Accepted Answer
2 weeks ago #225143

OK that's clear... but if I prepare the whole staging environnement, how do I then migrate all configurations/design/templates onto my production environnement ? I know for SP Page Builder I can easily export/import my pages, can I do the same e.g. for all mail templates ?

0
Atick Eashrak Shuvo
Atick Eashrak Shuvo
Accepted Answer
Support Agent 2 weeks ago #225154

Hello,

Yes, that is correct — some parts can be transferred, but not everything has a full export/import mechanism like SP Page Builder.

For EasyStore specifically:

  • Email templates are not part of a dedicated migration or export/import system, but they can be easily copied and pasted manually between environments
  • Configuration settings and design-related options are stored in the Joomla database and are environment-specific

This means that while certain elements (like SP Page Builder pages) can be moved easily, EasyStore configurations and setup-related options will still need to be recreated manually on the production site.

If needed, we can guide you on the most efficient way to replicate your staging setup in production to minimize manual work.

0