KB-2366 How to use the Migration Tool when Migrating to Appian Cloud

Kaushal Patel — Thu, 22 Jan 2026 15:19:15 GMT

Current Revision posted to Appian Knowledge Base by Kaushal Patel on 1/22/2026 3:19:15 PM

Purpose

Appian now provides infrastructure and a tool to assist with migrating data from self-managed environments into Appian Cloud. Appian will provision an AWS S3 bucket and encryption key in Appian Cloud’s AWS Environment, and provide credentials to securely transfer data into Appian Cloud.

These steps are meant for “Server Based” Appian, not Appian on Kubernetes (AoK).

Instructions

Download the migration tool from Forum. Follow the instructions here
Ensure you have received the Appian Cloud credentials from your Appian Support contact. Each Appian installation will have a different set of credentials
Add the following environment variables to each server of the Appian installation that is migrating to Appian Cloud. For step 3c, set the AWS_REGION environment variable to us-gov-east-1 if your Appian Cloud site resides in a GovCloud AWS region. Otherwise, set it to us-east-1.
1. export AWS_ACCESS_KEY_ID=<YOUR_ACCESS_KEY>
2. export AWS_SECRET_ACCESS_KEY=<YOUR_SECRET_ACCESS_KEY>
3. export AWS_REGION=<US-EAST-1 | US-GOV-EAST-1>
4. Utilize the --dry-run command below to check if the AWS credentials are setup properly
Run the migration tool on every server of the Appian installation that is migrating to Appian Cloud
1. Refer to some example commands below:
  1. ./migrate cloud export
    1. basic command
  2. ./migrate cloud export --help
    1. show the various arguments accepted by the script. Not all commands will be covered in this Knowledge Base article, so it is recommended to run --help
  3. ./migrate cloud export --dry-run
    1. validate your AWS credentials, and see a list of folders that will be migrated
    2. One of the first log messages should say “AWS Identity found”, and the identity should include “appian-cloud-migration”
  4. ./migrate cloud export -i /home/appian
    1. run a cloud export where Appian is installed at /home/appian
  5. ./migrate cloud export --db-dir <path-to-database-directory>
    1. migrate database data to Appian Cloud. This data should have previously been exported from your database, and stored in its own directory somewhere on one of your servers
2. Follow the prompts that the migration tool gives you. Enter ? to to get more information about each question
3. “Application server data” and “engine checkpoints data” only needs to be migrated once. Ensure that it is run on a server that runs the application server or engines, respectively.
Repeat steps 3 and 4 for each Appian installation that is migrating to Appian Cloud

Affected Versions

This article applies to all versions of "server based" self-managed Appian.

Last Reviewed: January 2026

Tags: administration, Migration

[DRAFT SUPP-1783] KB-XXXX How to use the Migration Tool when Migrating to Appian Cloud

dan.endean — Fri, 19 Dec 2025 16:05:51 GMT

Revision 8 posted to Appian Knowledge Base by dan.endean on 12/19/2025 4:05:51 PM

Purpose

These steps are meant for “Server Based” Appian, not Appian on Kubernetes (AoK).

Instructions

Download the migration tool from Forum. Follow the instructions here
Ensure you have received the Appian Cloud credentials from your Appian Support contact. Each Appian installation will have a different set of credentials
Add the following environment variables to each server of the Appian installation that is migrating to Appian Cloud. For step 3c, set the AWS_REGION environment variable to us-gov-east-1 if your Appian Cloud site resides in a GovCloud AWS region. Otherwise, set it to us-east-1.
1. export AWS_ACCESS_KEY_ID=<YOUR_ACCESS_KEY>
2. export AWS_SECRET_ACCESS_KEY=<YOUR_SECRET_ACCESS_KEY>
3. export AWS_REGION=<US-EAST-1 | US-GOV-EAST-1>
4. Utilize the --dry-run command below to check if the AWS credentials are setup properly
Run the migration tool on every server of the Appian installation that is migrating to Appian Cloud
1. Refer to some example commands below:
  1. ./migrate cloud export
    1. basic command
  2. ./migrate cloud export --help
    1. show the various arguments accepted by the script. Not all commands will be covered in this Knowledge Base article, so it is recommended to run --help
  3. ./migrate cloud export --dry-run
    1. validate your AWS credentials, and see a list of folders that will be migrated
    2. One of the first log messages should say “AWS Identity found”, and the identity should include “appian-cloud-migration”
  4. ./migrate cloud export -i /home/appian
    1. run a cloud export where Appian is installed at /home/appian
  5. ./migrate cloud export --db-dir <path-to-database-directory>
    1. migrate database data to Appian Cloud. This data should have previously been exported from your database, and stored in its own directory somewhere on one of your servers
2. Follow the prompts that the migration tool gives you. Enter ? to to get more information about each question
3. “Application server data” and “engine checkpoints data” only needs to be migrated once. Ensure that it is run on a server that runs the application server or engines, respectively.
Repeat steps 3 and 4 for each Appian installation that is migrating to Appian Cloud

Affected Versions

This article applies to all versions of "server based" self-managed Appian.

Last Reviewed: November 2025

Tags: administration, Migration

[DRAFT SUPP-1783] KB-XXXX How to use the Migration Tool when Migrating to Appian Cloud

dan.endean — Fri, 19 Dec 2025 16:03:45 GMT

Revision 7 posted to Appian Knowledge Base by dan.endean on 12/19/2025 4:03:45 PM

Purpose

These steps are meant for “Server Based” Appian, not Appian on Kubernetes (AoK).

Instructions

Download the migration tool from Forum. Follow the instructions here
Ensure you have received the Appian Cloud credentials from your Appian Support contact. Each Appian installation will have a different set of credentials
Add the following environment variables to each server of the Appian installation that is migrating to Appian Cloud
1. export AWS_ACCESS_KEY_ID=<YOUR_ACCESS_KEY>
2. export AWS_SECRET_ACCESS_KEY=<YOUR_SECRET_ACCESS_KEY>
3. Set the AWS_REGION environment variable to us-gov-east-1 if your Appian Cloud site resides in a GovCloud AWS region. Otherwise, set it to us-east-1.
  
  export AWS_REGION=<US-EAST-1 | US-GOV-EAST-1>
4. Utilize the --dry-run command below to check if the AWS credentials are setup properly
Run the migration tool on every server of the Appian installation that is migrating to Appian Cloud
1. Refer to some example commands below:
  1. ./migrate cloud export
    1. basic command
  2. ./migrate cloud export --help
    1. show the various arguments accepted by the script. Not all commands will be covered in this Knowledge Base article, so it is recommended to run --help
  3. ./migrate cloud export --dry-run
    1. validate your AWS credentials, and see a list of folders that will be migrated
    2. One of the first log messages should say “AWS Identity found”, and the identity should include “appian-cloud-migration”
  4. ./migrate cloud export -i /home/appian
    1. run a cloud export where Appian is installed at /home/appian
  5. ./migrate cloud export --db-dir <path-to-database-directory>
    1. migrate database data to Appian Cloud. This data should have previously been exported from your database, and stored in its own directory somewhere on one of your servers
2. Follow the prompts that the migration tool gives you. Enter ? to to get more information about each question
3. “Application server data” and “engine checkpoints data” only needs to be migrated once. Ensure that it is run on a server that runs the application server or engines, respectively.
Repeat steps 3 and 4 for each Appian installation that is migrating to Appian Cloud

Affected Versions

This article applies to all versions of "server based" self-managed Appian.

Last Reviewed: November 2025

Tags: administration, Migration

[DRAFT SUPP-1783] KB-XXXX How to use the Migration Tool when Migrating to Appian Cloud

Kaushal Patel — Wed, 12 Nov 2025 16:45:44 GMT

Revision 6 posted to Appian Knowledge Base by Kaushal Patel on 11/12/2025 4:45:44 PM

Purpose

These steps are meant for “Server Based” Appian, not Appian on Kubernetes (AoK).

Instructions

Download the migration tool from Forum. Follow the instructions here
Ensure you have received the Appian Cloud credentials from your Appian Support contact. Each Appian installation will have a different set of credentials
Add the following environment variables to each server of the Appian installation that is migrating to Appian Cloud
1. export AWS_ACCESS_KEY_ID=<YOUR_ACCESS_KEY>
2. export AWS_SECRET_ACCESS_KEY=<YOUR_SECRET_ACCESS_KEY>
3. Utilize the --dry-run command below to check if the AWS credentials are setup properly
Run the migration tool on every server of the Appian installation that is migrating to Appian Cloud
1. Refer to some example commands below:
  1. ./migrate cloud export
    1. basic command
  2. ./migrate cloud export --help
    1. show the various arguments accepted by the script. Not all commands will be covered in this Knowledge Base article, so it is recommended to run --help
  3. ./migrate cloud export --dry-run
    1. validate your AWS credentials, and see a list of folders that will be migrated
    2. One of the first log messages should say “AWS Identity found”, and the identity should include “appian-cloud-migration”
  4. ./migrate cloud export -i /home/appian
    1. run a cloud export where Appian is installed at /home/appian
  5. ./migrate cloud export --db-dir <path-to-database-directory>
    1. migrate database data to Appian Cloud. This data should have previously been exported from your database, and stored in its own directory somewhere on one of your servers
2. Follow the prompts that the migration tool gives you. Enter ? to to get more information about each question
3. “Application server data” and “engine checkpoints data” only needs to be migrated once. Ensure that it is run on a server that runs the application server or engines, respectively.
Repeat steps 3 and 4 for each Appian installation that is migrating to Appian Cloud

Affected Versions

This article applies to all versions of "server based" self-managed Appian.

Last Reviewed: November 2025

Tags: administration, Migration

[DRAFT SUPP-1783] KB-XXXX How to use the Migration Tool when Migrating to Appian Cloud

Kaushal Patel — Wed, 12 Nov 2025 16:43:23 GMT

Revision 5 posted to Appian Knowledge Base by Kaushal Patel on 11/12/2025 4:43:23 PM

Purpose

These steps are meant for “Server Based” Appian, not Appian on Kubernetes (AoK).

Instructions

Download the migration tool from Forum. Follow the instructions here
Ensure you have received the Appian Cloud credentials from your Appian Support contact. Each Appian installation will have a different set of credentials
Add the following environment variables to each server of the Appian installation that is migrating to Appian Cloud
1. export AWS_ACCESS_KEY_ID=<YOUR_ACCESS_KEY>
2. export AWS_SECRET_ACCESS_KEY=<YOUR_SECRET_ACCESS_KEY>
3. Utilize the --dry-run command below to check if the AWS credentials are setup properly
Run the migration tool on every server of the Appian installation that is migrating to Appian Cloud
1. Refer to some example commands below:
  1. ./migrate cloud export
    1. basic command
  2. ./migrate cloud export --help
    1. show the various arguments accepted by the script. Not all commands will be covered in this Knowledge Base article, so it is recommended to run --help
  3. ./migrate cloud export --dry-run
    1. validate your AWS credentials, and see a list of folders that will be migrated
    2. One of the first log messages should say “AWS Identity found”, and the identity should include “appian-cloud-migration”
  4. ./migrate cloud export -i /home/appian
    1. run a cloud export where Appian is installed at /home/appian
  5. ./migrate cloud export --db-dir <path-to-database-directory>
    1. migrate database data to Appian Cloud. This data should have previously been exported from your database, and stored in its own directory somewhere on one of your servers
2. Follow the prompts that the migration tool gives you. Enter ? to to get more information about each question
3. “Application server data” and “engine checkpoints data” only needs to be migrated once. Ensure that it is run on a server that runs the application server or engines, respectively.
Repeat steps 3 and 4 for each Appian installation that is migrating to Appian Cloud

Affected Versions

This article applies to all versions of "server based" self-managed Appian.

Last Reviewed: November 2025

Tags: administration, Migration

[DRAFT SUPP-1783] How to use the Migration Tool when Migrating to Appian Cloud

Patrick Hanley — Wed, 12 Nov 2025 16:15:27 GMT

Revision 4 posted to Appian Knowledge Base by Patrick Hanley on 11/12/2025 4:15:27 PM

Purpose

These steps are meant for “Server Based” Appian, not Appian on Kubernetes (AoK).

Instructions

Download the migration tool from Forum. Follow the instructions here
Ensure you have received the Appian Cloud credentials from your Appian Support contact. Each Appian installation will have a different set of credentials
Add the following environment variables to each server of the Appian installation that is migrating to Appian Cloud
1. export AWS_ACCESS_KEY_ID=<YOUR_ACCESS_KEY>
2. export AWS_SECRET_ACCESS_KEY=<YOUR_SECRET_ACCESS_KEY>
3. Utilize the --dry-run command below to check if the AWS credentials are setup properly
Run the migration tool on every server of the Appian installation that is migrating to Appian Cloud
1. Refer to some example commands below:
  1. ./migrate cloud export
    1. basic command
  2. ./migrate cloud export --help
    1. show the various arguments accepted by the script. Not all commands will be covered in this Knowledge Base article, so it is recommended to run --help
  3. ./migrate cloud export --dry-run
    1. validate your AWS credentials, and see a list of folders that will be migrated
    2. One of the first log messages should say “AWS Identity found”, and the identity should include “appian-cloud-migration”
  4. ./migrate cloud export -i /home/appian
    1. run a cloud export where Appian is installed at /home/appian
  5. ./migrate cloud export --db-dir <path-to-database-directory>
    1. migrate database data to Appian Cloud. This data should have previously been exported from your database, and stored in its own directory somewhere on one of your servers
2. Follow the prompts that the migration tool gives you. Enter ? to to get more information about each question
3. “Application server data” and “engine checkpoints data” only needs to be migrated once. Ensure that it is run on a server that runs the application server or engines, respectively.
Repeat steps 3 and 4 for each Appian installation that is migrating to Appian Cloud

Affected Versions

This article applies to all versions of "server based" self-managed Appian.

Last Reviewed: November 2025

Tags: administration, Migration

[DRAFT SUPP-1783] How to use the Migration Tool when Migrating to Appian Cloud

Patrick Hanley — Wed, 12 Nov 2025 16:13:26 GMT

Revision 3 posted to Appian Knowledge Base by Patrick Hanley on 11/12/2025 4:13:26 PM

Purpose

These steps are meant for “Server Based” Appian, not Appian on Kubernetes (AoK).

Instructions

Download the migration tool from Forum. Follow the instructions here
Ensure you have received the Appian Cloud credentials from your Appian Support contact. Each Appian installation will have a different set of credentials
Add the following environment variables to each server of the Appian installation that is migrating to Appian Cloud
1. export AWS_ACCESS_KEY_ID=<YOUR_ACCESS_KEY>
2. export AWS_SECRET_ACCESS_KEY=<YOUR_SECRET_ACCESS_KEY>
3. Utilize the --dry-run command below to check if the AWS credentials are setup properly
Run the migration tool on every server of the Appian installation that is migrating to Appian Cloud
1. Refer to some example commands below:
  1. ./migrate cloud export
    1. basic command
  2. ./migrate cloud export --help
    1. show the various arguments accepted by the script. Not all commands will be covered in this Knowledge Base article, so it is recommended to run --help
  3. ./migrate cloud export --dry-run
    1. validate your AWS credentials, and see a list of folders that will be migrated
    2. One of the first log messages should say “AWS Identity found”, and the identity should include “appian-cloud-migration”
  4. ./migrate cloud export -i /home/appian
    1. run a cloud export where Appian is installed at /home/appian
  5. ./migrate cloud export --db-dir <path-to-database-directory>
    1. migrate database data to Appian Cloud. This data should have previously been exported from your database, and stored in its own directory somewhere on one of your servers
2. Follow the prompts that the migration tool gives you. Enter ? to to get more information about each question
3. “Application server data” and “engine checkpoints data” only needs to be migrated once. Ensure that it is run on a server that runs the application server or engines, respectively.
Repeat steps 3 and 4 for each Appian installation that is migrating to Appian Cloud

Affected Versions

This article applies to all versions of "server based" self-managed Appian.

Last Reviewed: November 2025

Tags: administration, Migration

[DRAFT SUPP-1783] How to use the Migration Tool when Migrating to Appian Cloud

Patrick Hanley — Wed, 12 Nov 2025 16:13:09 GMT

Revision 2 posted to Appian Knowledge Base by Patrick Hanley on 11/12/2025 4:13:09 PM

Purpose

These steps are meant for “Server Based” Appian, not Appian on Kubernetes (AoK).

Instructions

Download the migration tool from Forum. Follow the instructions here
Ensure you have received the Appian Cloud credentials from your Appian Support contact. Each Appian installation will have a different set of credentials
Add the following environment variables to each server of the Appian installation that is migrating to Appian Cloud
1. export AWS_ACCESS_KEY_ID=<YOUR_ACCESS_KEY>
2. export AWS_SECRET_ACCESS_KEY=<YOUR_SECRET_ACCESS_KEY>
3. Utilize the --dry-run command below to check if the AWS credentials are setup properly
Run the migration tool on every server of the Appian installation that is migrating to Appian Cloud
1. Refer to some example commands below:
  1. ./migrate cloud export
    1. basic command
  2. ./migrate cloud export --help
    1. show the various arguments accepted by the script. Not all commands will be covered in this Knowledge Base article, so it is recommended to run --help
  3. ./migrate cloud export --dry-run
    1. validate your AWS credentials, and see a list of folders that will be migrated
    2. One of the first log messages should say “AWS Identity found”, and the identity should include “appian-cloud-migration”
  4. ./migrate cloud export -i /home/appian
    1. run a cloud export where Appian is installed at /home/appian
  5. ./migrate cloud export --db-dir <path-to-database-directory>
    1. migrate database data to Appian Cloud. This data should have previously been exported from your database, and stored in its own directory somewhere on one of your servers
2. Follow the prompts that the migration tool gives you. Enter ? to to get more information about each question
3. “Application server data” and “engine checkpoints data” only needs to be migrated once. Ensure that it is run on a server that runs the application server or engines, respectively.
Repeat steps 3 and 4 for each Appian installation that is migrating to Appian Cloud

Affected Versions

This article applies to all versions of "server based" self-managed Appian.

Last Reviewed: November 2025

[DRAFT SUPP-1783] How to use the Migration Tool when Migrating to Appian Cloud

Patrick Hanley — Wed, 12 Nov 2025 16:11:42 GMT

Revision 1 posted to Appian Knowledge Base by Patrick Hanley on 11/12/2025 4:11:42 PM

Purpose

These steps are meant for “Server Based” Appian, not Appian on Kubernetes (AoK).

Instructions

Download the migration tool from Forum. Follow the instructions here
Ensure you have received the Appian Cloud credentials from your Appian Support contact. Each Appian installation will have a different set of credentials
Add the following environment variables to each server of the Appian installation that is migrating to Appian Cloud
1. export AWS_ACCESS_KEY_ID=<YOUR_ACCESS_KEY>
2. export AWS_SECRET_ACCESS_KEY=<YOUR_SECRET_ACCESS_KEY>
3. Utilize the --dry-run command below to check if the AWS credentials are setup properly
Run the migration tool on every server of the Appian installation that is migrating to Appian Cloud
1. Refer to some example commands below:
  1. ./migrate cloud export
    1. basic command
  2. ./migrate cloud export --help
    1. show the various arguments accepted by the script. Not all commands will be covered in this Knowledge Base article, so it is recommended to run --help
  3. ./migrate cloud export --dry-run
    1. validate your AWS credentials, and see a list of folders that will be migrated
    2. One of the first log messages should say “AWS Identity found”, and the identity should include “appian-cloud-migration”
  4. ./migrate cloud export -i /home/appian
    1. run a cloud export where Appian is installed at /home/appian
  5. ./migrate cloud export --db-dir <path-to-database-directory>
    1. migrate database data to Appian Cloud. This data should have previously been exported from your database, and stored in its own directory somewhere on one of your servers
2. Follow the prompts that the migration tool gives you. Enter ? to to get more information about each question
3. “Application server data” and “engine checkpoints data” only needs to be migrated once. Ensure that it is run on a server that runs the application server or engines, respectively.
Repeat steps 3 and 4 for each Appian installation that is migrating to Appian Cloud

Affected Versions

This article applies to all versions of "server based" self-managed Appian.

Last Reviewed: November 2025