Migrate on-premises configurations to on-premises site

Last published : Oct 15, 2026
This article describes the steps to migrate your on-premises configurations from one site to another on-premises site using Automated Configuration Tool (ACT).

Requirements

  • Both on-premises sites must be domain joined to the same domain.
  • Use Citrix Virtual Apps and Desktops™ version 2305 or later.

Steps

  1. Download the Automated Configuration Tool and review the system requirements. See Download Automated Configuration.
  2. Open ACT and export your on-premises site using the following the command.
    Export-CvadAcToFile
    See Supported migration objects for the list of components supported for migration. For information on the steps to export, see Export on-premises configuration. The parent folder %HOMEPATH%\\Documents\\Citrix\\AutoConfig always contains the exported files from the most recent export.
  3. Launch the ACT on the target site. You must see an AutoConfig folder created in %HOMEPATH%\\Documents\\Citrix.
    Launch the ACT on the target site
  4. Copy the .yml files from the Export folder in the source site to the target site's %HOMEPATH%\\Documents\\Citrix\\AutoConfig folder.
    AutoConfig folder in target site
  5. Specify the environment that you are working in using the Set-CvadAcCustomerInfoFile command. For example:
    Set-CvadAcCustomerInfoFile -Environment OnPrem
    This command updates the CustomerInfo file with the environment.
    CustomerInfo file with set environment
  6. Migrate the configuration files using the following command.
    Import-CvadAcToFile
    If you want to import from a different folder rather than the AutoConfig folder, run the following:
    Import-CvadAcToFile -Sourcefolder PATH
    Note:
    If you are migrating host connections, then update the CvadAcSecurity.yml file with the connection information for each host type. See Update the security file for host connections.
    If you encounter any errors or exceptions, see the Fixups section in the log file.
  7. Verify that your configurations are migrated on your target site using Web Studio.