how to migrate on-prem running AEM 6.5 to another AEM server

[AkashCh2]

One of the AEM servers (Author) is facing a lot of segment corrupt node issues, I tried so many times to fix it but does not help, there is another option to start the AEM from previous checkpoints and I don't want to move backward.
So right now I want to move all the content, assets, and other configuration files to the new AEM instance.
can you guys help me to share some steps and suggestions to migrate successfully?

Note: We can not move the backup of the server to the new server and start the instance it will bring all corrupt segment nodes with it.

[EstebanBustamante · Accepted solution]

Hi, 

Let me give you some thoughts on how you can do it:

1. Identify Content and Assets: Begin by identifying all the content and assets that need to be migrated. This includes pages, assets, content fragments, experience fragments, tags, etc.

2. Backup Existing Data: Before making any changes, it's crucial to take a backup of the existing AEM instance. Even though you can't directly move the backup to the new server, having a backup ensures you have a fallback option in case anything goes wrong during the migration process.

3. Set Up New AEM Instance: Install and configure a new AEM instance on the target server. Ensure that the new instance is set up with the appropriate configurations, especially install if any external packages, and make sure is fully functional prior to migrating the content. For example, install the SP needed, ACS commons or other external bundles that are not part of the code

4. Export Content and Assets: Use AEM's built-in tools to export content and assets from the source AEM instance. You can use the Package Manager to create packages containing the content and assets you want to migrate.

5. Review and Clean Data: Before importing the data into the new AEM instance, review the exported packages and clean up any unnecessary or outdated content. This helps ensure that only relevant data is migrated, reducing the risk of bringing over corrupted or unwanted data.

6. Import Content and Assets: Once you've cleaned up the data, import the packages into the new AEM instance using the Package Manager. Make sure to carefully follow the import process and resolve any errors or conflicts that may arise during the import.

7. Verify Data Integrity: After importing the content and assets, thoroughly verify the data integrity in the new AEM instance. Test the websites, workflows, and any custom functionality to ensure everything is working as expected.

8. Migrate Configuration Files: Copy over any necessary configuration files from the old AEM instance to the new one. This includes configuration files for OSGi configurations that are not versioned (part of your code), replication agents, etc. Ensure that all configurations are properly updated to reflect any changes in environment.

9. Update References and Paths: If the new AEM instance has a different URL structure or file paths, make sure to update any references to URLs or file paths in your content and code accordingly.

10. Perform Testing and Validation: Once the migration is complete, perform comprehensive testing and validation to ensure that all aspects of the application are functioning correctly in the new environment. This includes testing functionality, performance, and security.

11. Monitor and Troubleshoot: Monitor the new AEM instance closely after migration to identify any potential issues or performance bottlenecks.

12. Documentation and Knowledge Transfer: Document the migration process and any custom configurations or settings applied during the migration. 

Hope this helps.

[pulkitvashisth]

Here are some steps how we can migrate your stuff to a fresh AEM instance  

1. Pick your source (corrupted AEM) and target (clean AEM).
2. Decide what content to move (avoid anything funky). Package Share Manager or Content Transfer Tool (CTT) , you can chose between these.
3. Schedule downtime for both instances.
4. Move the content - CTT is great for picking specific paths (avoid those segments!). Package Share Manager works if your content structure is sweet.
5. For assets Manually copy them if they're in the file system, or use CTT to grab them.
6. Configurations - grab OSGi configs from version control and import them to the target. Manual work might be needed for some things.
7. Test everything after the move

[Sudheer_Sundalam]

@AkashCh2 ,

Adding to the points mentioned by @EstebanBustamante  and @pulkitvashisth , You also need to move the users and groups from the current author to the new Author server.

You may use ACL Package manager from ACS-Commons library to package and move the users and groups.

https://adobe-consulting-services.github.io/acs-aem-commons/features/packagers/acl-packager/index.ht...

Thanks,

Sudheer.

[DPrakashRaj]

I would still insist that after taking a backup you can still for repository consistency check and she how old it shows you the consistent data and if it’s good to go or you really want to migrate the data to new instance.

to setup an new instance of prod you need to identify all the changes that was done directly on aem instance like

• osgi configs
• user and group and its ACLs
• Custom log configs
• custom indexes 
• any aem OOTB workflow change 
• workflow and log purge configs
• Service pack and acs-commons if any

to migrate the content and dam I would suggest using crx2oak tool as it’s fast in comparison to package manager. https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/upgr...

[MayurSatav]

@AkashCh2 , Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

[EstebanBustamante]

@AkashCh2 Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community