Follow these basic steps to update your Digital Publishing Suite (DPS) app to an Experience Manager Mobile (AEM Mobile) app.

Step 1: Learn AEM Mobile

DPS and AEM Mobile are separate systems with different workflows and distribution environments. Before you update your app, make sure that you understand the workflow and capabilities of AEM Mobile.

Getting started with AEM Mobile

Feature list comparison for AEM Mobile platforms

Step 2: Create a project

If you are an existing DPS customer, you or your company should have received an email notification with information about signing in to the Portal ( If you have not received this information, contact Adobe by sending a message to

Individually or as a team, set up your account, create your project, and assign roles to users.

Make sure that you set up analytics to work with AEM Mobile. It is not possible to have AEM Mobile analytics data go into DPS report suites. For AEM Mobile apps, data collection is done in a new report suite.

Creating projects for AEM Mobile

Account administration for AEM Mobile

Analytics for AEM Mobile

Step 3: Migrate folios to the project

If it makes sense to migrate folios to your AEM Mobile project, use the Folio Migration Tool to migrate folios to your project. Migrating folios does not affect the folios in a DPS account or the associated application. A copy of the content is added to the AEM Mobile project. See Migrating content from DPS folios.

Folio migration guidance

  • At a general rule, migrate only the folios that will be used as back issues. If you plan to edit the articles of the migrated articles, consider re-creating the articles in AEM Mobile instead of migrating the folios.
  • At first, migrate only one folio at a time. Clean up the migrated content as needed before migrating more folios. Consider selecting all articles in a collection and bulk-editing them to add a keyword so that you can filter content more easily in the On-Demand Portal.
  • Decide whether to open the new collection to a Browse Page or Content View. By default, folios are migrated as collections with Content View selected. If you change the collection to open to a Browse Page, resolve redundant covers and table of contents articles, and consider replacing low-resolution article images.
  • Add metadata to articles for card mapping and portal filtering.
  • Check Article Access settings (Free, Metered, or Protected) for articles that appear in non-free collections.
  • Consider deleting duplicate articles used in multiple folios, such as “Credits” or “Using This App.” In AEM Mobile, you can use the same article in multiple collections.
  • Resolve articles that refer to Reading APIs, such as geolocation, app detection, and camera APIs.
  • Consider replacing HTML article files for improved reflow on different platforms and devices. Migrated HTML articles have fixed dimensions. In AEM Mobile, responsive HTML articles can reflow to fill the screen without letterboxing.
  • If you need to edit the source document of a migrated article, update your navto links to reflect the new Article Name, not the previous DPS Article Name.

Step 4: Update product IDs, subscriptions, and entitlement

To ensure that existing app users still have access to previously purchased content, the Product IDs in the AEM Mobile project setup should match the Product IDs in the DPS setup, and AEM Mobile availability dates should match the DPS publication dates.

When you migrate a folio, the Product ID for that folio is added to the collection. When you publish the collection, the Product is added to the Products & Subscriptions section of the Portal, with settings preserved. For example, the Availability Date is the same as the migrated folio's Publication Date. In AEM Mobile, you can assign the same Product ID to multiple collections.

In AEM Mobile, you cannot publish a collection in which the product's Availability Date is set in the future. If you have set the folio's Publication Date in the future in order to make that folio appear at the top of the library, reset the Availability Date in the Portal.

In AEM Mobile, Product IDs for subscriptions are not included in the app. Instead, specify your existing Subscription IDs in the Products & Subscriptions section of the Portal. In AEM Mobile, you can offer either Standard or All Access subscriptions.

If your existing DPS app includes direct entitlement, you might be able to use the same v2 direct entitlement server for your AEM Mobile app, depending on its setup. For example, if you use DPS 2014-specific APIs or information such as accounts or folio names, you'll need to update the entitlement server configuration.

In-app purchases and subscriptions for AEM Mobile apps

Entitlement for AEM Mobile

Step 5: Build the app

To replace the existing app in the iOS App Store or Google Play Store, use the same App ID/Bundle ID for the AEM Mobile app that you used for the previous app. If you use a different Bundle ID, it will be treated as a different app rather than a updated version of the same app.

For iOS apps, use iTunes Connect to submit a new version of the app. For details, see iOS Publishing Guide for AEM Mobile.

Make sure that you submit a version that's higher than the current app version. For details, see Changing the AEM Mobile app version number.

Building iOS apps for AEM Mobile

Building Android apps for AEM Mobile

Building Windows apps for AEM Mobile