You begin the migration of objects (services and activities) with the very first step of exporting them to a zip file at a location specified by you. You can export the objects by using the export.xml file. To export activities:

You can also automate the migration process through a CD pipeline by using a tool such as Jenkins.

Copy the export.xml file from shared repository ${SHARED_PATH}$/migration/template and paste at ${SHARED_PATH}$/migration/custom location.

Open export.xml in a text editor, and do the followings.

Provide the location where you want to create the export zip along with the file name in the <TargetZipLoc> tag, for example, $SHARED_PATH$/migration/export/export-$TIMESTAMP$.zip.
- $SHARED_PATH$ is an environment variable that contains the configured shared path.
- $TIMESTAMP$ is current timestamp appended to the zip file in the format dd-mm-yyyy_hh-mm-ss. to help you filter the zip files based on timestamp.
Specify the activity you want to export. Type A to export all activities or a specific activity and PR to export based on the projects in the <ExportType> tag.

Type the group name to which activity belongs in the <Groups> tag. In connect migration, we can export objects of 1 group at a time, so no option to define multiple groups.

Attribute	Definition
name	Enter group name whose activities you want to export in the <Groups> tag, for example, Group_1.
activityRefId	Set the activity id of the group, for example, 001 for 'Group_1'.
projectRefId	Set the project id of the group, for example, 001 for 'Group_1'.

If export type is A then only activityRefId will be consider.

If Export type is PR then only projectRefId will be consider.

Define the list of projects that you want to export. You can export the activities of more than one Project.

Attribute	Definition
projectRefId	Set the project id and this should match with projectRefId defined in the <Groups> tag while exporting the activities based on the projects.
export	Set the value yes or no to define either you want to export the activities of the specific project or not.

Define the activity type that you want to export under <Activities> tag.

You can define multiple activity types as you want. For reference, the list of all activity types is defined in the export.xml file.
If you want to export specific activity then add the name or activityid under the specified Activity type. The format of ActivityId is: <id>ActivityID</id>. The format of name is: <name>Name</name>.

Here you also get the flexibility of exporting Transactions and Process flows along with their dependencies.
Wildcard characters (“*” and “?”) are also supported in the name of the activity.
“*” stands for zero or more characters and “?” stands for a single character. If an activity name under the <name> tag for a particular object contains either of the two characters then all the objects at the source end matching the <name> before “*”(and multiple characters after it) and all characters before “?” (and only one character after it) that belongs to the exported group will be migrated.
For example,
For exporting all File Source activities starting with “FS_” you need to specify the following:
```
<activity type="FileSource">
   <name>FS_*</name>
</activity>
```
For exporting File Source activities with activity id = “010000036202128947281839100086” and “010000036202133067542452000039”, you need to specify the following:
```
<activity type="FileSource">
   <id>010000036202128947281839100086</id>
   <id>010000036202133067542452000039</id>
</activity>
```

Define the list of folders or files that you want to export with criteria. You can use these attributes for including or excluding multiple files/sub-folders.

All of the following attributes support wildcards. You can also use multiple wildcards separated by commas (,). If no values are specified for Folder attribute, it considers the whole folder by default.

Attribute	Definition
includeSubFolders	To export the specified folder including all the sub-folders.
excludeSubFolders	To export the specified folder excluding the sub-folders.
includeFiles	To export including files.
excludeFiles	To export excluding files.

Save the file.

Provide values for the following properties and environment variables in values.yaml file as shown in the table below.

Variable/Property	Value
BACKEND_DB_URL	<URL of the backend database server>
BACKEND_DB_USERNAME	<Username of your backend database server>
BACKEND_DB_PASSWORD	<Password for your backend database server>
BACKEND_DB_DRIVER_CLASS	<Backend database driver class name>
BACKEND_DB_TYPE	<Type of the backend database server. (for example, SQL-server)>
SHARED_PATH	<environment variable that contains the configured shared path. (for example, /shared)>
MIGRATION_XML_FILE_PATH	<Path of the export.xml. (for example, ${SHARED_PATH}$/migration/custom/export.xml)>
image.pullSecret.registry	<URL of the repository>
volumes.claimName	<Name of the PV claim>
Infra.secret	<Name of the Secret>

Navigate to the migration directory, and run the below command to export the objects.
```
helm upgrade -i migration adeptia/migration -f adeptia/values.yaml -n <NAMESPACE>
```
After you perform these steps, the export zip file will be created at the defined target location.

The Migration job does not get deleted automatically after the migration is complete. You need to manually delete it before you start a new migration process.

You may be interested in...

What is newApplication architectureKey termsInstallUsage scenarios

What is new
Application architecture
Key terms
Install
Usage scenarios

Browser not supported