In this article
...
Use the Project Migration API to migrate a SnapLogic Project from one Org to another.
| Note |
|---|
When you migrate a Project more than once, the existing assets are overwritten. You might have to associate your Tasks with the correct Pipelines after the migration. Typically, even after multiple migrations, account references remain intact in the Pipeline, but we recommend that you verify all references before starting your Pipeline executions. |
HTTP Request
POST api/1/rest/public/project/migrate/<project_pathname>
Parameters
| Parameter Name | Description | Default Value | Example | ||
|---|---|---|---|---|---|
| dest_path | The path of the target destination.
| N/A | "/myotherorg/clientprojects/sales" | ||
| asset_types | A list of the asset types to be included in the Project for migration. | N/A | ["File", "Job", "Account", "Pipeline"] | ||
| async_mode | If true, then the request is returned immediately with message to wait for motd notification. | true | "false" | ||
| duplicate_check | If true, then the request raises a conflict error if the Project with the same name exists in the specified destination path. | true | "false" | ||
| content-type | Binary header specifying the content type. Since all SnapLogic assets are JSON files, this parameter's value must always be application/json.
| application/json | "application/json" |
...