Skip to main content

Varicent ELT Help Center

Migration

Abstract

Move objects like pipes, connections, and data sources across organizations. Select the objects to migrate from a source organization to a target organization.

Move objects like pipes, connections, and data sources across organizations. Select the objects to migrate from a source organization to a target organization.

For example, you want to move new logic from your source to your target environment since it's ready for you to use. The source environment is your staging environment, and your target environment is your production environment. You need the pipes and their data sources for the new logic to work. You have approximately 300 pipes and 200 files, tables, and data sources. With this much logic to move, the Migration wizard saves you time in migrating the objects.

First, select the source organization. Next, select the sources to migrate, including the dependent objects, and select the options for migrating credentials. Migrating all of the objects and credentials helps save you time, as the Migration wizard does it all for you at one time.

Then, the Migration wizard shows the total number of objects you're migrating. During the review phase, review the actions carefully and make any necessary changes, such as if an object is being overwritten that shouldn't be. For example, if you find an object being overwritten and it shouldn't be, you can click the Back button and update the objects to migrate.

As you migrate your logic, you can see the actions the Migration wizard is performing. This applies to both new and subsequent migrations:

Table 9. Migration actions

Action

Description

Migration type

New

The object (pipe, data and dependent objects) exist in the source but not in the target organization.

New migrations

Exists

The object (pipe, data and dependent objects) exist in both the source and target organizations with no changes.

Subsequent migrations

Overwriting

The object (pipe, data and dependent objects) exist in both the source and target organizations with differences.

Subsequent migrations

Delete

The object (pipe, data and dependent objects) does not exist in the source organization.

Subsequent migrations



After you start the migration process, you will see the status of your migration on the Migration page:

Table 10. Migration statuses

Status

Description

In Progress

The migration is currently running.

Failed – System Error

The migration encountered an unexpected system failure.

Timed Out

The migration stopped because the execution time was greater than 30 minutes.

{#} Warning

The migration has some connections that are missing credentials.

Success

The migration finished without issues, and all selected objects were migrated.