Hi @sai1278 ,

Once you have integrated dynamic media with AEM, you may need to reprocess existing images within AEM in order to send them to DM. However, new images will be automatically pushed to DM.

Even with DM correctly set up, all images uploaded, and the CDN in place, your website may not automatically deliver images via DM. To activate this feature, you will need to "Enable DM features" for the image core component. To do this, go to the template and enable the DM feature in the image component policies.
For reprocessing of existing images so that they can be migrated to dynamic media, please follow below link:

https://www.danklco.com/posts/2022/08/bulk-asset-reprocessing-in-aem-as-a-cloud-service-assets.html

Hope it helps!


Thanks
Tarun

Using Dynamic Media with AEM Sites Core Components

https://experienceleague.adobe.com/en/docs/experience-manager-learn/assets/dynamic-media/dm-with-aem-sites/dynamic-media-core-components

Refer to "Configure Image Component to use Dynamic Media" mark in the Video. 

Hi @sai1278 ,

Upgrading from Scene7 Classic to Dynamic Media involves several steps to ensure a smooth transition and to update existing logic pointing to static renditions and the old S7 Classic URLs. Here's a general guide to help you through the process:

1. Inventory of Existing Assets: Start by taking an inventory of all assets currently hosted on Scene7 Classic. This includes images, videos, 3D assets, and any other media assets that will need to be migrated to Dynamic Media.

2. Migration of Assets: Migrate the assets from Scene7 Classic to Dynamic Media. This process may involve bulk migration tools provided by Adobe or manual migration depending on the size and complexity of your asset library.

3. Update URLs: Update all references to static renditions and Scene7 Classic URLs in your application code, templates, and content. Replace these URLs with the corresponding URLs from Dynamic Media.

4. Testing: Thoroughly test your application after updating the URLs to ensure that all assets are loading correctly from Dynamic Media. Test across different devices, browsers, and scenarios to verify the functionality.

5. Smart Crop Integration: If you are leveraging smart crop functionality, ensure that your application code is updated to utilize the smart crop URLs provided by Dynamic Media.

6. Training and Documentation: Provide training to your team members on the new Dynamic Media features and workflows. Update documentation and knowledge base articles to reflect the changes.

7. Performance Optimization: Take advantage of Dynamic Media's capabilities for performance optimization, such as lazy loading, image compression, and CDN integration, to improve the performance of your application.

8. Monitoring and Maintenance: Regularly monitor the performance and usage of Dynamic Media in your application. Address any issues or optimizations as needed to ensure optimal performance and user experience.

9. Go Live: Once testing is complete and everything is functioning as expected, deploy the updated application to production and go live with Dynamic Media.

10. Post-Launch Support: Provide ongoing support to your team members and users as they transition to using Dynamic Media. Address any feedback or issues that arise post-launch.

By following these steps and thoroughly testing your application before and after the upgrade, you can ensure a successful transition from Scene7 Classic to Dynamic Media and leverage its full suite of features for your digital assets.

@sai1278 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.