You can migrate, or reproduce, content from published Digital Publishing Suite (DPS) folios to articles in collections. Note that migrating folios does not affect any of the original DPS folio settings or content.

To migrate content, you need a DPS Application account with published folios, and you need a Master account with a Master Admin or a user account with content production permissions.

If the migration is successful, your project will include a new collection for each folio, and each article from the DPS folio will be converted into an article in the On-Demand Portal.


At this time, migrated articles do not support layouts that reference Reading API features.

When not to migrate folios

As a general rule, you should re-create articles in AEM Mobile instead of migrating them in these situations:

  • If your articles include navto links between articles and you plan to edit the source files after migration. When you migrate a folio, the resulting articles include different Article Name values. The navto links work in the resulting AEM Mobile articles, but there is a mismatch between the source files and the migrated articles. If you want to edit the source files, you'll need to update the navto links to point to the new Article Name values.
  • If your folio includes HTML articles. Migrated HTML articles are locked into a specific dimension, such as 768x1024, resulting in unnecessary letterboxing. If you create HTML articles in AEM Mobile, no letterboxing occurs. See Creating HTML articles for AEM Mobile.

App migration strategy

See Strategies for upgrading a DPS app.

Conference video (low audio)

Bob Bringhurst delivered this session at the Adobe MAX 2015 conference:

Making the Move (1:34:02)

  1. Sign in to the On-Demand Portal ( using an Adobe ID with content creation permissions, and click Folio Migration Tool.

  2. In the Folio Migration Tool section, click Migrate.


  3. Sign in using an Adobe ID with a DPS Application role.

  4. Select the folios you want to migrate.

    Folios must be published as Public.

    A maximum of 25 folios are supported per request. However, if you need to edit the migrated article settings, consider migrating fewer folios at a time in order to simplify the editing process.

  5. In the right panel of options, select the target project (if there’s more than one).

  6. Indicate whether you want to import vertical or horizontal layouts from dual-orientation folios. (You cannot import vertical layouts into horizontal articles or horizontal layouts into vertical articles.)

  7. For article thumbnail images, indicate whether you want to use existing TOC images, which are usually 70x70 pixels, or generate an image from the first page of the article.

    Selecting the “First Page Thumbnail” option might result in thumbnail images that are more suitable for cards. With either option, you can replace the thumbnail image when editing the article.

    Thumbnail image options
  8. If you have migrated the folio previously, select "Force overwrite already migrated articles" if you want to replace existing articles. Deselect this option if you want to migrate new versions of existing articles.

  9. Click Migrate.

    Wait until the migration is complete before starting a new migration.

  10. After a few minutes, return to the Portal and open the target publication. Edit the new collection and articles as needed. 

    For example, you might want to edit your collection to display a browse page instead of content view, and you might want to replace thumbnail images.

A new collection is created from the DPS folio, and the articles within that folio are created in the Content & Layouts of the Portal and added to the collection. If a folio includes sections, each section is migrated as a sub-collection. Article metadata is converted where possible. "Tags" metadata is converted as internal keywords.

You can then publish these articles and the collection.