Yes, instead of running the unified tool, i followed these steps mentioned here: https://github.com/adobe/aem-cloud-service-source-migration/tree/master/packages/repository-modernizer

Hi, I am trying with the index converter as mentioned here https://github.com/adobe/aem-cloud-service-source-migration/tree/master/packages/index-converter#configurations Tool ran successfully, but the filter.xml generated without any index . Where can we check the converted indexes as i cannot see ...

i do have the path

Hi Team, I am running Repository Modernizer as referred here: https://github.com/adobe/aem-cloud-service-source-migration/tree/master/packages/repository-modernizer My source maven project is of archetype 19 and getting below error:********** Executing Repository Modernizer ********** Restructuring ...

It worked .Thank you

Hi, I am trying to run  aio plugins:install @adobe/aio-cli-plugin-cloudmanagerBut i am getting the following error :warning ..\..\..\..\package.json: No license field error An unexpected error occurred: "https://registry.npmjs.org/@adobe%2faio-cli-plugin-aem-cloud-service-migration/@adobe%2faio-cli-...

Hi, If we consider migrating to AEMaaCS, how and what are the considerations/modifications for datastore/nodestore and how they will be migrated to AEMaaCS? Ex: If i use a fileDataStore how it is migrated to AEMaaCS.

Thanks for the reply, My current AEM version is 6.4 and uses archtype 13 and if i need to migrate to cloud i need to upgrade to latest archtype and then follow the migration process?

thanks Anudeep_Garnepudi , so it means if i use archtype 19 in aem 6.4 then to migrate i need to upgrade the archtype?

Hi , Could some one help with the archetype compatibility for the using the AEMaaCS?