2.4.7-p8 Compatibility / Housekeeping / Merge Changes from PR 20 by ssx · Pull Request #24 · opengento/magento2-downgrade-ee-ce

ssx · 2025-12-31T10:24:29Z

#20

…able

…ge SQL Update README

ssx · 2025-12-31T12:09:12Z

@thomas-kl1 scripts all working now, just going to do some further testing.

thomas-kl1

Thank you very much @ssx for your contribution and improvments!

I've posted a few comments, and open to discussion and I'm looking forward to merge this PR once they are resolved!

Thank you again! 😃

thomas-kl1 · 2025-12-31T14:07:00Z

+-- 03_cms.sql
+-- 
+
+update cms_page set creation_time = update_time WHERE `creation_time` LIKE '%0000%';


Could you uppercase SQL keywords please? (UPDATE + SET)

Also what situation could lead to this one? (a short comment on top of the query is fine)

another that came from the other PR :)

IMO we should remove this line

thomas-kl1 · 2025-12-31T14:08:42Z

+-- ALTER TABLE `magento_banner_catalogrule`
+--     DROP FOREIGN KEY `MAGENTO_BANNER_CATRULE_RULE_ID_SEQUENCE_CATRULE_SEQUENCE_VAL`;


Can we remove this commented query? The table magento_banner_catalogrule is removed in ee.sql

or add a short comment on top of it with the reason why

thomas-kl1 · 2025-12-31T14:11:53Z

+-- Amasty related
+CALL PROC_DROP_FOREIGN_KEY("amasty_ampromo_rule", "AMASTY_AMPROMO_RULE_SALESRULE_ID_SALESRULE_ROW_ID");
+CALL PROC_DROP_FOREIGN_KEY("amasty_amrules_rule", "AMASTY_AMRULES_RULE_SALESRULE_ID_SALESRULE_ROW_ID");
+CALL PROC_DROP_FOREIGN_KEY("amasty_amrules_usage_limit", "AMASTY_AMRULES_USAGE_LIMIT_SALESRULE_ID_SALESRULE_ROW_ID");
+CALL PROC_DROP_FOREIGN_KEY("amasty_free_gift_timer_timer_data", "AMASTY_FREE_GIFT_TIMER_TIMER_DATA_SALESRULE_ID_SALESRULE_ROW_ID");
+CALL PROC_DROP_FOREIGN_KEY("amasty_amrules_usage_counter", "AMASTY_AMRULES_USAGE_COUNTER_SALESRULE_ID_SALESRULE_RULE_ID");
+CALL PROC_DROP_FOREIGN_KEY("amasty_banners_lite_banner_data", "AMASTY_BANNERS_LITE_BANNER_DATA_SALESRULE_ID_SALESRULE_RULE_ID");
+CALL PROC_DROP_FOREIGN_KEY("amasty_banners_lite_rule", "AMASTY_BANNERS_LITE_RULE_SALESRULE_ID_SALESRULE_ROW_ID");
+CALL PROC_DROP_FOREIGN_KEY("amasty_banners_lite_rule", "AMASTY_BANNERS_LITE_RULE_SALESRULE_ID_SALESRULE_RULE_ID");


anything related to third party module should be moved to a dedicated file so it's up to anyone to run this one or not (ex: 99_amasty.sql)

your problem there will be that the need running early on so that the products one can run without issue (maybe 00_amasty.sql instead)

thomas-kl1 · 2025-12-31T14:17:33Z

    ADD CONSTRAINT `SALESRULE_CUSTOMER_RULE_ID_SALESRULE_RULE_ID` FOREIGN KEY (`rule_id`) REFERENCES `salesrule` (`rule_id`);
+
+--
+-- Already done above in line 103.


isn't it line 111?

We should regroup the operation over the same table in the same group of queries for more clarity

thomas-kl1 · 2025-12-31T14:20:54Z

    ADD CONSTRAINT `CAT_PRD_BNDL_SELECTION_OPT_ID_CAT_PRD_BNDL_OPT_OPT_ID` FOREIGN KEY (`option_id`) REFERENCES `catalog_product_bundle_option` (`option_id`) ON DELETE CASCADE ON UPDATE RESTRICT;

 ALTER TABLE `catalog_product_bundle_selection_price`
+-- 	DROP INDEX `CATALOG_PRODUCT_BUNDLE_SELECTION_PRICE_WEBSITE_ID`, -- we do not need to remove this index


could you add a quick explanation?

we could remove this line IMO

thomas-kl1 · 2025-12-31T14:21:48Z

 DELETE c.* FROM `catalog_url_rewrite_product_category` c LEFT JOIN catalog_product_entity p ON c.product_id = p.entity_id WHERE p.entity_id IS NULL;
 ALTER TABLE `catalog_url_rewrite_product_category`
    DROP FOREIGN KEY `CAT_URL_REWRITE_PRD_CTGR_PRD_ID_SEQUENCE_PRD_SEQUENCE_VAL`,
+--     DROP FOREIGN KEY `FK_BB79E64705D7F17FE181F23144528FC8`, -- maybe we have to remove this key instead of the previous one


was it related to your tests?

that came from the original other PR

It may depends on builds, sometimes the FK are not generated with the name from the declarative schema (or setup schema)

might be worth wrapping it in the func then, so it can run if it's there, otherwise ignore it

agreed! but I'm not sure that this key name refer to the same FK (I should browse my projects and check)

thomas-kl1 · 2025-12-31T14:21:51Z

 DELETE FROM `cataloginventory_stock_item` WHERE `product_id` NOT IN (SELECT `entity_id` FROM `catalog_product_entity`);
 ALTER TABLE `cataloginventory_stock_item`
    DROP FOREIGN KEY `CATINV_STOCK_ITEM_PRD_ID_SEQUENCE_PRD_SEQUENCE_VAL`,
+--     DROP FOREIGN KEY `CATINV_STOCK_ITEM_STOCK_ID_CATINV_STOCK_STOCK_ID`, -- maybe we have to remove this key instead of the previous one


was it related to your tests?

that came from the original other PR

Ok, my bad didn't paid attention to it! it's safe to remove this line, we should'nt remove the relation for the stock ID anyway

@thomas-kl1 no worries :D

ssx · 2025-12-31T14:37:39Z

@thomas-kl1 I'll pick them up ASAP - most came from the other PR rather than me. Happy to drop those out.

amarroni · 2026-02-18T14:50:12Z

@thomas-kl1 I'm in the middle of discovery for a downgrade. When you think this merge can be merged?

thomas-kl1 · 2026-02-18T15:11:25Z

@ssx are you still willing to work on these changes?
Depending on @ssx answer, @amarroni you may want to pick some of the job here?

Otherwise I would need to do it myself, but that could mean not before next week

ssx · 2026-02-19T12:22:32Z

@thomas-kl1 @amarroni I am! this is in my diary tomorrow to continue on!

ssx · 2026-02-20T15:47:24Z

@ssx are you still willing to work on these changes? Depending on @ssx answer, @amarroni you may want to pick some of the job here?

Otherwise I would need to do it myself, but that could mean not before next week

Hello @thomas-kl1 @amarroni I've been working on https://github.com/DeployEcommerce/magento2-ee-to-community-tool today. Basically, a drop in tool to run through these for you. Currently testing on a 2.4.7 and the DB side appears to be working perfectly. Happy for the changes in the sql/ directory there to be lifted out!

thomas-kl1 · 2026-02-20T16:24:10Z

Hi @ssx
In my opinion the tools would be benefit being unified and not confuse the community.
As this repo benefit a great visibility, would you like to move your changes here and being the maintainer of the repo?
Let me know your thoughts as I don't how we could mirrored the changes regarding the sql scripts in an easy and secure way without manual actions.

BTW Opengento is an association and not a company, so we don't benefit any commercial values here.

amarroni · 2026-02-20T18:20:36Z

@ssx @thomas-kl1 hi guys how are you?
@ssx I just check the migration tool and looks greate! I was working (with 🤖 ) similar tool. If you want I can add or suggest somthing to be check. Patch List, when you run Setup Registry. I create a a third party extensions analyzer in order to take care of the Commerce extension and how should be the best way to migrate this modules.

I'll testing the tool in a fresh magento open source and fresh magento commercer installation and I'll let you know how was.

ssx · 2026-02-23T08:23:16Z

Hi @ssx In my opinion the tools would be benefit being unified and not confuse the community. As this repo benefit a great visibility, would you like to move your changes here and being the maintainer of the repo? Let me know your thoughts as I don't how we could mirrored the changes regarding the sql scripts in an easy and secure way without manual actions.

BTW Opengento is an association and not a company, so we don't benefit any commercial values here.

Hi @thomas-kl1! :)

Once I've finished testing and @amarroni too - I'll port all of the SQL changes here for you as well. At some point I'll switch out the sql directory in the tool for this repo and use that instead so everyone benefits 🙂

volodymyr-vynnyk and others added 2 commits April 28, 2025 15:16

Migrate Magento from EE 2.4.5 to Magento CE 2.4.7-p3

7a7cc60

Merge branch 'master' of github.com:studioraz/magento2-downgrade-ee-ce

18d29eb

ssx mentioned this pull request Dec 31, 2025

Migrate Magento from EE 2.4.5 to Magento CE 2.4.7-p3 #20

Open

ssx added 8 commits December 31, 2025 10:43

Don't include Amasty in here

3224d7f

Rename files into the order they should be processed in

7a0cd54

Remove orphan pages

f24ff02

Don't try to remove a table thats already gone

4d3f5b6

Add fixes for Salesrule migration

8d657f4

Tidy up DROPs and revert change to category_catalog_category_entity t…

439995d

…able

Add headers into scripts to ensure right order of cat generates a lar…

69ab2cb

…ge SQL Update README

Fix product script to only remove keys when they exist

8fad440

ssx changed the title ~~Merge Changes from PR 20~~ 2.4.7-p8 Compatibility / Merge Changes from PR 20 Dec 31, 2025

ssx changed the title ~~2.4.7-p8 Compatibility / Merge Changes from PR 20~~ 2.4.7-p8 Compatibility / Housekeeping / Merge Changes from PR 20 Dec 31, 2025

thomas-kl1 self-requested a review December 31, 2025 14:05

thomas-kl1 self-assigned this Dec 31, 2025

thomas-kl1 requested changes Dec 31, 2025

View reviewed changes

thomas-kl1 assigned ssx Dec 31, 2025

		-- ALTER TABLE `magento_banner_catalogrule`
		-- DROP FOREIGN KEY `MAGENTO_BANNER_CATRULE_RULE_ID_SEQUENCE_CATRULE_SEQUENCE_VAL`;

Conversation

ssx commented Dec 31, 2025

Uh oh!

ssx commented Dec 31, 2025

Uh oh!

thomas-kl1 left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

ssx commented Dec 31, 2025

Uh oh!

amarroni commented Feb 18, 2026

Uh oh!

thomas-kl1 commented Feb 18, 2026

Uh oh!

ssx commented Feb 19, 2026

Uh oh!

ssx commented Feb 20, 2026

Uh oh!

thomas-kl1 commented Feb 20, 2026

Uh oh!

amarroni commented Feb 20, 2026

Uh oh!

ssx commented Feb 23, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants