Cloud customer?
Start for Free >
Upgrade in MyJFrog >
What's New in Cloud >





Post Migration Actions Overview

After you complete the migration from self-hosted JPD to JFrog Cloud, ensure that you check the configurations that are not applied on JFrog Cloud. We recommend that you review the list before migration to ensure that you are ready for changes required after the migration process is complete.


Page Contents

Post Migration Checklist

The following table lists the configurations that you need to check and update if required after migration.

ConfigurationIssueAction
Remote RepositoriesThird-party connections might require validation.Validate that any third-party tools that work with the self-hosted platform works after migration to JFrog Cloud. You might need to whitelist the JFrog Cloud IP in the third-party system.
Federated RepositoriesThird-party connections might require validation.Validate that any third-party tools that work with the self-hosted platform works after migration to JFrog Cloud. You might need to whitelist the JFrog Cloud IP in the third-party system.
Virtual RepositoriesThird-party connections might require validation.Validate that any third-party tools that work with the self-hosted platform works after migration to JFrog Cloud. You might need to whitelist the JFrog Cloud IP in the third-party system.
ProxiesProxy configuration is not migrated.Check the proxy configuration in the source JFrog Platform and recreate the configuration in JFrog Cloud.
Reverse ProxiesReverse Proxy configuration is not migrated.Check the reverse proxy configuration in the source JFrog Platform and recreate the configuration in JFrog Cloud.
fileUploadMaxSizeMbfileUploadMaxSizeMb is set to the default value in JFrog Cloud

No action required.

You cannot customize the fileUploadMaxSizeMb value in JFrog Cloud.

BackupsYou cannot create backups in JFrog Cloud.

No action required.

JFrog Cloud automatically takes backups of the instance.

Replications ConfigurationThird-party connections might require validation.Validate that any third-party tools that work with the self-hosted platform works after migration to JFrog Cloud. You might need to whitelist the JFrog Cloud IP in the third-party system.
Server NameThe server name for JFrog Cloud instance is set when you create the instance.You can keep the same name as the self-hosted JFrog Platform server before you create the JFrog Cloud instance.
Offline Mode in Remote RepositoriesThe offline mode is set as OFF.You can set offline mode as ON after the migration is complete.
Archive Search EnabledArchive Search Enabled is set as False.Discuss with support before the migration since it can impact the CPU load during migration.
Mail ServerMail server configuration is replaced with JFrog Cloud mail server configuration.

No action required.

Since JFrog Cloud handles sending emails there is no need for a custom email server setup.

Xray ConfigReplaced with JFrog Cloud default.

No action required.

You cannot use a different configuration other than the configuration defined by JFrog Cloud.

LDAP SettingsThe settings are migrated but disabled by default to prevent a lockout after migration if there are connectivity issues.

You can enable the settings if required after migration.

Password Settings

Password settings are changed but the existing passwords are not impacted. The default JFrog Cloud settings are applied. 

A token that works with source JFrog Platform will not be respected in JFrog Cloud post-migration. The user needs to enter the credentials.

You can change the password settings after migration to the configure that you desire. For more information, see General Security Settings.
HTTP SSO SettingsHTTP SSO settings are disabled in JFrog Cloud

No action required.

HTTP SSO is supported in JFrog Cloud.

Crowd SettingsThe settings are migrated but disabled by default to prevent a lockout after migration if there are connectivity issues.You can enable the settings if required after migration.
SAML SettingsThe settings are migrated but disabled by default to prevent a lockout after migration if there are connectivity issues.You can enable the settings if required after migration.
OAUTH SettingsThe settings are migrated but disabled by default to prevent a lockout after migration if there are connectivity issues.You can enable the settings if required after migration.
User Lock PolicyReplaced with JFrog Cloud default.You can change the settings after migration to the configure that you desire. For more information, see General Security Settings.
SSH Server SettingsSSH server settings are not migrated.

No action required.

SSH server settings are not supported.

System PropertiesSystem Properties are set to the default JFrog Cloud values.Discuss with support before the migration.
Base URLThe base URL is set by JFrog Cloud.

No action required.

JFrog Cloud provides the base URL.

Federated Repository Base URLThe Federated Repository base URL is set by JFrog Cloud.

No action required.

JFrog Cloud provides the Federated Repository Base URL.

Folder Download ConfigurationFolder Download is set to disabled.You can enable the setting if required after migration.
Remote ReplicationsThird-party connections might require validation.Validate that any third-party tools that work with the self-hosted platform works after migration to JFrog Cloud. You might need to whitelist the JFrog Cloud IP in the third-party system.
Local ReplicationsThird-party connections might require validation.Validate that any third-party tools that work with the self-hosted platform works after migration to JFrog Cloud. You might need to whitelist the JFrog Cloud IP in the third-party system.
Retention Settings (Trash Can Settings)Trash Can is set to disabled.You can enable the setting if required after migration.
  • No labels
Copyright © 2022 JFrog Ltd.