Date Format discrepency for a Locale in On-Prem and Pega Cloud - Blocker issue

Currently my team is working on a cloud migration for a client. We are facing one blocker regarding date formatting.

Issue: default date format for en_SG is different in on prem and cloud environment.

MM/dd/yyyy in prem and dd/MM/yyyy for on cloud. Because of this we are facing issues with properties where property is text and UI control is datetime.

Is there a way to update default date format en_SG locale? and what could be the root cause for the wrong format in On-Prem environment. Client has tightly coupled code to expect date in MM/dd/yyyy format and there might be issue with in-flight cases in UAT, Pre-Prod and Prod

The Date conversions will be handled through Pega Data migrate team during the cut over to match with Pega Cloud expected format. Could you please check with data migration team ? This will be done on STG (during the dry run) and PROD (Final cut over).

The problem is that the DB colomn is Varchar, and this is the scenario in multiple places and we have no way to identify all the DB tables and colomns

I think you have to work with your DBAs to identify the potential places where varchar is defined for the date fields and work with the data migration team to come up with a strategy during the data migration.