Skip to main content
H
HardBalloon
Level 1
May 26, 2026
Solved

Experience fragment - copy folder to another live copy location

  • May 26, 2026
  • 1 reply
  • 28 views

Hello Adobe-community,

 

Adobe has introduced the live-copy behavior in experience fragments and it has cause an issue with our current structure - but we have a plan to fix it.

 

For context, we have a lot of forms that exist in our project and they all live under language-masters:

/content/experience-fragments/…/language-masters/forms

 

We have two live copies and we’ll need to copy all of the forms under LM to a new location:
/content/experience-fragments/…/<country-code>/forms

 

Based on our playing-experience, (issue) we aren’t able to create a live-copy for all the forms in one go.

 

Has anyone experienced this or does anyone know how to get around this?

 

Any ideas will help,

HardBalloon

Best answer by SubbaraoGa1

​@HardBalloon 
 

We've reviewed this and it does look like a known product behavior rather than something specific to your implementation.

Adobe's current direction for Experience Fragments is to use MSM/live copy rather than direct copying, and in newer AEM versions that support extends to both individual Experience Fragments and folders. However, in practice, creating a very large XF live copy structure in a single operation can still be unreliable, especially for large folders, because the operation is not handled asynchronously.

For your case, the recommended approach would be:

  1.  Do not try to create a live copy of the entire `/language-masters/forms` tree in one go.
  2. Split the forms into smaller logical subfolders or batches.
  3. Create the live copies batch-by-batch into `/content/experience-fragments/.../<country-code>/forms`.
  4. If this is only a one-time migration and you do not need ongoing inheritance, create the live copies and then detach them afterward.

Also, we would avoid using direct copy as the main migration method, since Adobe recommends live copy for XFs and direct copying can create issues in some cases, especially where Target export metadata is involved.

So the short answer is: yes, this is something others have run into, and the safest workaround is to migrate the forms in smaller batches rather than trying to live-copy the full forms structure in a single step.

 

1 reply

Jineet_Vora
Community Advisor and Adobe Champion
Jineet_VoraCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
May 26, 2026

Hi ​@HardBalloon,


Can you check if this helps https://experienceleague.adobe.com/en/docs/experience-cloud-kcs/kbarticles/ka-27079?lang=en

S
Adobe Employee
SubbaraoGa1Adobe EmployeeAccepted solution
Adobe Employee
May 27, 2026

​@HardBalloon 
 

We've reviewed this and it does look like a known product behavior rather than something specific to your implementation.

Adobe's current direction for Experience Fragments is to use MSM/live copy rather than direct copying, and in newer AEM versions that support extends to both individual Experience Fragments and folders. However, in practice, creating a very large XF live copy structure in a single operation can still be unreliable, especially for large folders, because the operation is not handled asynchronously.

For your case, the recommended approach would be:

  1.  Do not try to create a live copy of the entire `/language-masters/forms` tree in one go.
  2. Split the forms into smaller logical subfolders or batches.
  3. Create the live copies batch-by-batch into `/content/experience-fragments/.../<country-code>/forms`.
  4. If this is only a one-time migration and you do not need ongoing inheritance, create the live copies and then detach them afterward.

Also, we would avoid using direct copy as the main migration method, since Adobe recommends live copy for XFs and direct copying can create issues in some cases, especially where Target export metadata is involved.

So the short answer is: yes, this is something others have run into, and the safest workaround is to migrate the forms in smaller batches rather than trying to live-copy the full forms structure in a single step.

 

    Terms & ConditionsAccessibility statement

    Loading footer...