![cloning-1](https://i0.wp.com/techtrantor.com/wp-content/uploads/2021/01/cloning-1.png?resize=496%2C381&ssl=1)
The new Oracle Integration Cloud feature to Import/Export brings additional capabilities when it comes to quickly setting up a new environment.
![](https://i0.wp.com/techtrantor.com/wp-content/uploads/2021/01/cloning-1.png?resize=496%2C488&ssl=1)
This is not meant for Code promotion nor CI/CD – this is an easy way to fully clone an environment.
I have an OIC instance running in the London region, and I want to bring all of the Connections, Integrations, Lookups, Processes into a new instance running in Frankfurt region.
Configure Storage
The first step in enabling the Import/Export, is to setup the Storage connectivity. We will connect with the Oracle Object Storage.
Go to: Settings>Storage
Swift URL: https://swiftobjectstorage.<region>.oraclecloud.com/v1/<object-storage-namespace>/<bucket>
See here how to create a bucket.
User Name: This is the OCI username. If you are a federated user it will look like:oracleidentitycloudservice/<myemail>@oracle.com
Password: This is not the OIC password – it’s an API Token – check here on how to get one.
![](https://i0.wp.com/lh3.googleusercontent.com/-WtTnibMjc4s/X6KDIBh1_GI/AAAAAAAAY6k/SM6q_ZRRVZIx7fd2tfmQNeGMLyAYNpk1wCLcBGAsYHQ/s16000/image.png?w=678&ssl=1)
The next step is to create an Export job that will store all the artefacts in the Object Storage.
Create an Export Job
Go to: Settings>Import/Export>Export
Provide a Job Name, a Description, and choose if you want to export the Security Artefacts.
![](https://i0.wp.com/lh3.googleusercontent.com/-3kocG68k_Ik/X6KC8vtEyKI/AAAAAAAAY6g/HbgF23wBTfwiZZoocFVrM5AChaAeNorSACLcBGAsYHQ/s16000/image.png?w=678&ssl=1)
Once the Export Job finished, the Object is successfully stored in the Object Storage Bucket.
![](https://i0.wp.com/lh3.googleusercontent.com/-D6JuLPPB3DM/X6UxcWjQnOI/AAAAAAAAY9o/BC7yl63WxwQ8fbdbA7lPnQe4TqFNR3bqgCLcBGAsYHQ/s16000/image.png?w=678&ssl=1)
Create an Import Job
The second part is the Import of these artefacts into the new instance. In a similar manner, the Storage connectivity needs to be setup first, and then the Import Job can be created.
There are a couple of extra options, as one can choose to Activate and/or Start Scheduled Integrations.
![](https://i0.wp.com/lh3.googleusercontent.com/-XsbNNgaZcp0/X6KG5eTAs-I/AAAAAAAAY64/rmxP1woyz8oX5yd4mBqcy8K0CXb4v29dwCLcBGAsYHQ/s16000/image.png?w=678&ssl=1)
Once the Import is complete, you will find a Summary with the details, and all of the imported artefacts are available for usage in the new instance.
![](https://i0.wp.com/lh3.googleusercontent.com/-kzVuO1Fsr0k/X6KKG1Du3RI/AAAAAAAAY7E/shcHV4B9TxwqTj8fJLSsyOqCSjx0cFAxwCLcBGAsYHQ/s16000/image.png?w=678&ssl=1)
As Initially stated, this is not meant to CI/CD nor code promotion between environments. It’s an easy way to store the full set of artefacts from one instance, and if needed, to import everything into a new instance.