Batch Migration

​

Overview

​

Prerequisites

1. Golden Pages created for each target template type — see Golden Pages Guide
2. Design System patterns ingested from those Golden Pages — see Design Pattern Ingestion
3. Target pages created in AEM — the destination pages should already exist in your content structure
4. Source URLs accessible — Gradial needs to read from your source pages

​

Migration Workflow Overview

┌─────────────────┐     ┌─────────────────┐     ┌─────────────────┐
│  1. Prepare     │     │  2. Create      │     │  3. Run         │
│  Spreadsheet    │ ──▶ │  Batch Task     │ ──▶ │  Batch          │
└─────────────────┘     └─────────────────┘     └─────────────────┘
                                                        │
┌─────────────────┐     ┌─────────────────┐            │
│  5. Promote     │     │  4. Review      │            │
│  Launches       │ ◀── │  Results        │ ◀──────────┘
└─────────────────┘     └─────────────────┘

​

Step 1: Prepare Your Migration Spreadsheet

​

Required Columns

​

Optional Columns

• Pattern Recommendations — Specify which Design System patterns to use for each page
• Site Group — For sites with dynamic content segmentation
• Template Reference — Explicitly specify which template to use
• Custom metadata — Any page-specific information the agent should know

​

Writing Effective Instructions

Migrate the content from the Live Link URL to the Migrated Page Path.

Use the Article Page Design Patterns for component selection.

Map content as follows:
- Page hero: Use "Article Hero" pattern with the main headline and featured image
- Body content: Use "Rich Text Block" pattern for article text
- Related articles: Use "Card Grid 3-Column" pattern for any linked articles
- CTA section: Use "Promo Banner" pattern for any call-to-action blocks

Preserve all existing images and upload to DAM at /content/dam/mysite/articles/

Do not run the QA agent after completion.

​

Pattern Recommendations

Patterns to use:
- "Article Hero" for the top banner section
- "Rich Text Block" for main body content  
- "Pull Quote" for any highlighted quotes
- "Image Gallery" for photo collections
- "Related Content Cards" for the bottom section

​

Step 2: Create the Batch Task

​

Navigate to Batch Tasks

​

Configure the Batch

1. Enter a descriptive name for the batch (e.g., “Blog Migration - January 2025”)
2. Add an optional description
3. Verify the correct Workspace and Environment are selected

Tip: For initial testing, name your batch clearly (e.g., “Blog Migration - TEST RUN”) so you can easily identify and clean up test batches later.

​

Import Your Spreadsheet

1. Click Bulk Add to open the import screen
2. Select New Page as the task type
3. Upload your Excel file containing the migration data
4. The first row will be used as headers; each subsequent row becomes a task

​

Configure Task Properties

• Assignee — Who owns these tasks
• Approver — Who reviews completed tasks
• Template — The AEM template to apply

​

Create Tasks

Important: Creating tasks does not run them. Review the imported tasks before executing the batch.

​

Step 3: Run a Test Batch First

​

Why Test First?

• Verify your instructions produce the expected results
• Check that patterns render correctly
• Identify any adjustments needed to your spreadsheet
• Avoid having to fix issues across hundreds of pages

​

Running Selected Tasks

1. From the batch task table, select specific tasks using the checkboxes
2. Click Run Batch — only selected tasks will execute
3. Review results before running the full batch

​

Evaluating Test Results

1. Click into each task to see the instructions and results
2. Open the AEM Authoring Agent report to see what actions were taken
3. Preview the migrated page in AEM to verify content and layout
4. Note any adjustments needed for your instructions or pattern recommendations

​

Step 4: Run the Full Batch

​

Execute the Batch

1. Click Run Batch from the batch task view
2. The button shows the total number of tasks to process
3. Confirm to start processing

​

Monitor Progress

• Progress bar showing overall batch completion percentage
• Task list with status indicators for each task:
  • 🔵 Running — Task is being processed
  • 🟢 Done — Task completed successfully
  • 🔴 Error — Task encountered an issue

​

Processing Time

1. Read and analyze the source page
2. Map content to appropriate patterns
3. Create or update the destination page in AEM
4. Upload any assets to the DAM
5. Optionally run QA checks

​

Step 5: Review and Promote

​

Review Completed Tasks

1. Navigate back to the task list
2. Click into individual tasks to review:
   • The original instructions
   • The agent’s action report
   • Any summary messages or QA findings

​

Promote Launches

1. Select tasks ready for promotion (individually or use the header checkbox to select all visible)
2. Click Promote Launches
3. For batches with multiple pages of tasks, navigate to each page and repeat

Note: Promoting a launch does NOT publish the page. Publication still follows your organization’s standard AEM workflow and governance processes.

​

Handle Issues

• Create follow-up tasks in Gradial to make corrections
• Use Content Updates for copy changes, component adjustments, or styling fixes
• Iterate until pages meet quality standards

​

Best Practices

​

Spreadsheet Preparation

• Be detailed in instructions — More context produces better results
• Specify patterns explicitly — Don’t rely on the agent to guess which patterns to use
• Include all URLs — Provide both author and preview URLs for easy verification
• Test your spreadsheet — Run a small batch first to validate your setup

​

Batch Organization

• Use clear naming conventions — Makes tracking and cleanup easier
• Group similar pages — Batch pages that use the same template and patterns together
• Keep batches manageable — Consider splitting very large migrations into multiple batches

​

Quality Assurance

• Review before promoting — Check migrated pages in AEM preview
• Use the QA agent — Let Gradial flag potential issues automatically
• Plan for iteration — Expect some pages will need follow-up adjustments

​

Execution

• Test first, always — Run 1-2 pages before the full batch
• Monitor progress — Watch for errors during batch execution
• Promote in batches — Review and promote pages in manageable groups

​

Troubleshooting

​

Related Resources

• Golden Pages Guide — Creating reference pages for pattern ingestion
• Design Pattern Ingestion — Setting up your Design System
• New Page Workflow — Creating individual new pages
• Content Updates — Making changes to existing pages
• Batch Updates — Updating multiple pages at once