AEM 6.5 LTS: Upgrade 6.5.1 to 6.5.2 | Community
Skip to main content
Magicr
Magicr
Level 6
July 16, 2026
Question

AEM 6.5 LTS: Upgrade 6.5.1 to 6.5.2

  • July 16, 2026
  • 2 replies
  • 38 views

 I have an running AEM 6.5.1 LTS instance that contains a lot of own content and code packages, as well as own configurations. Now  I want to upgrade this instance to 6.5.2. I download the release service pack and figured out, the “service pack” is a jar and not a single zip file.

My current experience is when I execute this jar file I will get an instance with default and lose my content. 

Does not really exists another way? 

    2 replies

    chaudharynick
    chaudharynick
    Level 4
    July 16, 2026

    Hi ​@Magicr 

    can you please check software distribution and look for service pack package. it should be available as content package

    BrianKasingli
    Community Advisor and Adobe Champion
    BrianKasingliCommunity Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    July 16, 2026

    You will not lose your existing content simply because the service pack is provided as a JAR.

    For AEM 6.5 LTS, there are two possible approaches:

    1. In-place upgrade

      Replace the existing Quickstart JAR with the new SP2 JAR and start it against the existing crx-quickstart repository. Your content, configurations and installed packages remain in the existing repository.

      Adobe documentation:
      https://experienceleague.adobe.com/en/docs/experience-manager-65-lts/content/implementing/deploying/upgrading/in-place-upgrade

    2. Sidegrade using Oak-upgrade

      Create a separate AEM 6.5 LTS instance and migrate the repository content using Oak-upgrade.

      Adobe documentation:
      https://experienceleague.adobe.com/en/docs/experience-manager-65-lts/content/implementing/deploying/upgrading/aem-65-to-aem-65lts-content-migration-using-oak-upgrade

    However, the Oak-upgrade document is specifically written for migrating from AEM 6.5 to AEM 6.5 LTS. For a normal AEM 6.5 LTS SP1 to SP2 update, the in-place Quickstart JAR upgrade is the more direct approach.

    Running the new JAR in an empty directory creates a new default instance. For an in-place upgrade, it must be used with your existing crx-quickstart repository.

    Take a complete backup and test the upgrade in a lower environment before upgrading production.

      Magicr
      MagicrAuthor
      Level 6
      July 17, 2026

      Thanks for your answer. I tried the first step. I used the command “-unpack”. After this, a new jar file was created in crx-quickstart/app. I deleted the old one and started my instance again. Result: The file error.log contains a lot of errors. When I called my updated instance via browser nothing works, except the system console. The overview page for bundles shows me a lot of stopped ones (I guess more than twenty) and I’m unable to start those.

      Terms & ConditionsAccessibility statement

      Loading footer...