You can migrate your Adaptive Forms, themes, templates, and cloud configurations from AEM 6.4 Forms on OSGi and AEM 6.5 Forms on OSGi to AEM as a Cloud Service. Before migrating these assets, use the Migration Utility to convert the format used in the earlier versions to the format used in AEM as a Cloud Service. When you run Migration Utility, the following assets are updated:
The service helps migrate content from only AEM Forms on OSGi environments. Migrating content from AEM Forms on JEE to a Cloud Service environment is not supported.
(Only for AEM 6.3 Forms or a previous version environment upgraded to AEM 6.4 Forms or AEM 6.5 Forms) Adaptive Forms based on out-of-the-box templates and themes available in AEM 6.3 Forms or previous version are not supported on [!DNL AEM Forms] as a Cloud Service.
In a Cloud Service environment, the Migration Utility works in conjunction with the User Mapping Tool and Content Transfer Tool. The Migration Utility makes AEM Forms assets compatible with Cloud Service and the content transfer tool migrates the content from your AEM Forms environment to an AEM as a Cloud Service environment. Before using the Migration Utility, learn the process of moving to AEM as a Cloud Service. The process has two tools:
Accounts with administrator privileges on AEM Forms as a Cloud Service and your local AEM Forms environment.
Download and install Best Practice Analyzer, Content Transfer Tool, and AEM Forms Migration Utility from Software Distribution Portal
Run the Best Practices Analyzer tool and fix the reported issue.
Perform the following steps to make your AEM Forms assets compatible with Cloud Service and transfer them to an AEM as a Cloud Service environment.
Create a clone of your existing AEM Forms environment.
Always use the cloned environment to run the Content Transfer Tool and the Migration Utility. Content Transfer Tool and Migration Utility make some changes to the content and assets. So, do not run the Content Transfer Tool and the Migration Utility on a production environment.
Log in to your cloned environment with administrative privileges.
Run the User Mapping Tool to map your users with corresponding Adobe IMS user accounts. You require Adobe IMS user accounts to login to a AEM Forms as a Cloud Service instance.
Download and install the Content Transfer Tool and AEM Forms as a Cloud Service Migration Utility from Software Distribution Portal on the cloned environment. You can use AEM Package Manager to install the tool and the utility.
Navigate to Tools > Operations > Content Migration.
Open the Prepare Forms for migration card. The browser displays five options:
Use the option one-after another to make your AEM Forms assets compatible with AEM as a Cloud Service:
Tap AEM Forms Assets Migration, and in the next screen, tap Start Migration. It makes Adaptive Forms and themes on your AEM Forms environment compatible with AEM as a Cloud Service .
Tap Adaptive Forms Custom Components Migration and in the Custom Components Migration page, tap Start Migration. It makes any custom component developed for Adaptive Forms and component overlays on your AEM Forms environment compatible with AEM as a Cloud Service .
Tap Adaptive Forms Template Migration and in the Custom Components Migration page, tap Start Migration. It makes Adaptive Form templates at /apps or /conf and created using AEM Template Editor compatible with AEM as a Cloud Service .
Tap AEM Forms Cloud Configurations Migration and then on the Configuration Migration page, tap Start Migration. It updates and moves the following Cloud Services to a new location:
Tap Code Editor Script Migration, specify a location to save reusable functions, and tap **Start Migration.
The Cloud Service does not support rule editor scripts. The Code editor script migration tool converts all rule scripts on your environment to reusable functions and applies the reusable functions to visual editor at appropriate location. These reusable functions are saved in the form of client libraries and help you keep existing functionality intact. The tool automatically applies the generated reusable functions to corresponding Adaptive Forms.
Use the Package Manager to export the reusable functions (Client Libraries) to a package.
Run the Content Transfer Tool. While specifying parameters on the Create Migration Set screen, specify the path of Adaptive Forms, themes, templates, Form Data Models, Cloud Services, Custom Components and other AEM Forms-specific assets to the Paths to be included option. It adds specified AEM Forms assets to migration set.
Adaptive Forms: You can find adaptive forms at
/content/dam/formsanddocuments/and /content/forms/af. For example, for an adaptive form titled WKND Registration add paths
Form Data Mode: You can find all the Form Data Models at
/content/dam/formsanddocuments-fdm. For example,
Client libraries: The default path of client libraries is
Adaptive Form templates: The default path of templates is
/conf/<template folder>. For example, for a template titled basic add path
Adaptive Form themes and Client libraries: The default path of themes is
/content/dam/formsanddocuments-themes/ and default path of client libraries is
/etc/clientlibs/fd/theme. For example, for a template titled WKND Theme add path
/content/dam/formsanddocuments-themes/wkndtheme and client libraries for the theme at
/etc/clientlibs/reference-themes/wkndtheme-3-0. You can also have themes and client libraries at other custom paths.
Cloud Configurations: You can find Cloud Configurations at
/conf/. For example, Form Data Model cloud configuration is at
Workflow Model: You can find AEM Workflow Models at
/conf/global/settings/workflow/models/. For example, for an workflow model titled WKND Registration add path
You can add top level folder paths listed below or specific folder paths as described below. It enables you to migrate a certain assets and all the assets and forms at once.
To migrate AEM Workflow models, specify the following paths: