@narendiran_ravi Sorry that I missed your specific requirement. We recently moved back from AMS to On Prem for a client. We did it with collaboration from Adobe CSE who helped in sharing the AWS Images of AEM repos which we set up again on the vanilla setup of On Prem AEM Servers. We did few code changes, IP rules update but overall it avoided the need to move assets, content seperately. But when it comes to AEMAACS the whole underlying infrsturcture is different. Try to compare what is compatible with On prem AEM 6.5 what is not compatible against what you have on AEMAACS, which gives you a clear picture on strategising your migration approach. This will be custom based approach based on your implementation. You need to consider migration of Assets, User ACLs, Workflows, Scheduled Jobs, Tags etc.