The Migration utility converts the Adaptive Forms assets, cloud configrurations, and Correspondence Management assets from the format used in the earlier versions to the format used in AEM 6.4 Forms. When you run migration utility, the following are migrated:
In case of out of place upgrade, for case of Correspondence Management assets, you can run the migration every time you import the assets. For Correspondence Management migration you need to have the Forms Compatibility Package installed.
You can upgrade to the latest version of AEM Forms 6.4 from AEM Forms 6.3 or 6.2 or perform a fresh installation. Depending on whether you upgraded your previous installation or performed a fresh install, you need to do one of the following:
In case of in-place upgrade
If you performed an in-place upgrade, the upgraded instance already has the assets and documents. However, before you can use the assets and documents, you will need to install AEMFD Compatibility package (includes Correspondence Management Compatibility package)
Then you need to update the assets and documents by running the Migration utility.
In case of out of place installation
If it is an out of place (fresh) installation, before you can use the assets and documents, you will need to install AEMFD Compatibility package (includes the Correspondence Management Compatibility package).
Then you need to import your asset package (zip or cmp) on the new setup and then update the assets and documents by running the Migration utility. Due to backward compatibility-related changes, locations of a few folders in crx-repository are changed. Manually export and import dependencies (custom libraries and assets) from previous setup to fresh environment.
For Correspondence Management assets:
Run the Migration utility before making any changes in the assets or creating assets. We recommend that you do not run the utility after making any changes or creating assets. Make sure that the Correspondence Management or Adaptive Forms Assets user interface is not open while the migration process is running.
When you run the Migration Utility for the first time, a log is created with the following path and name:
\[aem-installation-directory]\cq-quickstart\logs\aem-forms-migration.log. This log keeps getting updated with Correspondence Management and Adaptive Forms migration info, such as moving of assets.
Before running the migration utility, ensure that you have taken a backup of your crx repository.
In a browser session, log in to AEM author instance as an Admin.
Open the following URL in the browser:
The browser displays four options:
Do the following to perform the migration:
To migrate assets, tap AEM Forms Assets Migration, and in the next screen, tap Start Migration. The following get migrated:
During assets migration, you may find warning messages such as “Conflict found for…”. Such messages indicate that rules for some of the components in adaptive forms could not be migrated. For example, if the component had an event which had both rules and scripts, if rules occur after any script none of the rules for the component are migrated. However, such rules can be migrated by opening the rule editor in adaptive form authoring.
These components can be migrated by opening them in Rule Editor in Adaptive Forms editor.
To migrate rules and scripts (not required if upgrading from 6.3) in custom components, tap Adaptive Forms Custom Components Migration, and in the next screen, tap Start Migration. The following get migrated:
To migrate templates (not required if upgrading from 6.3), tap Adaptive Forms Template Migration, and in the next screen, tap Start Migration. The following get migrated:
To migrate adaptive form custom components, tap Adaptive Forms Custom Components Migration and in the Custom Components Migration page, tap Start Migration. The following get migrated:
To migrate adaptive form templates, tap Adaptive Forms Template Migration and in the Custom Components Migration page, tap Start Migration. The following get migrated:
Migrate AEM Forms Cloud Configuration services to leverage the new context-aware cloud service paradigm, which includes the touch enabled UI (under /conf). When you migrate AEM Forms Cloud Configuration services, the cloud services in /etc are moved to /conf. If you do not have any cloud services customizations that depend on the legacy paths (/etc?lang=en), it is recommended that you run the migration utility right after upgrading to 6.4 and use cloud configuration Touch UI for any further work. If you have any existing cloud services customizations, continue using classic UI on upgraded setup until the customizations are updated to align with the migrated paths (/conf?lang=en) and then run the migration utility.
To migrate AEM Forms cloud services, which include the following, tap AEM Forms Cloud Configuration Migration (cloud config migration is independent of AEMFD Compatibility package), tap AEM Forms Cloud Configurations Migration and then on the Configuration Migration page, tap Start Migration:
Form Data Model cloud services
Typekit cloud services
The browser window displays the following as the migration process takes place:
When executed, the Migration utility does the following:
If you are upgrading from 6.2 to 6.4, for Correspondence Management, new folders may appear in the UI that include your assets. You may need to check these folders to locate your assets.
After the Migration utility finishes running, proceed to the housekeeping tasks.
After running the Migration utility, take care of the following housekeeping tasks:
Ensure that XFA version of layouts and fragment layouts is 3.3 or later. If you are using layouts and fragment layouts of an older version, then there could be issues in rendering the letter. To update version of an older XFA to the latest version, complete the following steps:
Publish all the assets that were published in the previous system before migration. The migration utility updates the assets only on the author instance and to update the assets on the publish instance (s) you need to publish the assets.
In AEM Forms 6.4, some of the rights of the forms users groups are changed. If you want any of your users to be able to upload XDPs and Adaptive Forms containing scripts or use code editor, you need to add them to forms-power-users group. Similarly, template-authors can no longer use the code editor in Rule Editor. For users to be able to use code editor, add them to af-template-script-writers group. For instructions on adding users to groups, see Managing Users and User Groups.