Migration and automation | Migrate doc based authoring pages to UE page | Community
Skip to main content
New Member
June 23, 2025

Migration and automation | Migrate doc based authoring pages to UE page

  • June 23, 2025
  • 2 replies
  • 360 views

Dear Folks,

 

I am using universal editor in AEMAaCS, I need to move sharepoint doc based authoring pages (around 2000 pages) to UE(universal editor) site structure. Is there any tool/plugin in AEM supports to automatically create site structure? Or do I need to create all 2000 pages manually? 

 

Assume all the doc based authoring blocks are created in UE compatible github repository. 

 

What I am looking:

1. Automatic page conversion and migration

2. Minimal or no authoring tweaks after migration

3. No pages loss during migration 

 

Looking for experts advise.

 

Thanks,

Pradeep

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

SantoshSai
Community Advisor
Community Advisor
June 23, 2025

Hi @pradeepdu,

To address your points:
  1. Automatic Page Creation & Migration
    There's no out-of-the-box Adobe tool that directly converts SharePoint pages to UE pages. However, you can automate page creation using AEM APIs like PageManager#create, combined with reading from your GitHub content using a custom AEM service or a migration script (Groovy, Java, or Node-based).

    You can also consider leveraging Adobe's Content Transfer Tool, although it’s meant for on-prem to cloud migration and may need customization for UE page structures.

  2. Minimal Authoring Tweaks
    If your components are fully UE-compatible and content is structured properly in the repo, you can reduce authoring to near zero. Just ensure your JSON metadata, template types, and editable templates are all aligned.

  3. No Page Loss
    To avoid data loss, always perform a dry run in lower environments and include validation logic in your script (e.g., confirm each page exists post-creation, log any skipped entries).

Recommendation:
  • Write a custom migration utility (OSGi or standalone) that:

    • Reads content block files from GitHub

    • Creates pages using the appropriate template under your site structure

    • Populates each page using Sling POST servlet or JCR APIs

Santosh Sai
arunpatidar
Community Advisor
Community Advisor
July 1, 2025