orchestrator
2024.10
true
- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Storing Robot Credentials in CyberArk
- Storing Unattended Robot Passwords in Azure Key Vault (read only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read only)
- Storing Unattended Robot Credentials in AWS Secrets Manager (read only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- Configuring automation capabilities
- Audit
- Resource Catalog Service
- Automation Suite robots
- Folders Context
- Automations
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Managing Storage Buckets
- Moving Bucket Data Between Storage Providers
- Test Suite - Orchestrator
- Integrations
- Troubleshooting
Moving Bucket Data Between Storage Providers
Orchestrator User Guide
Last updated Nov 13, 2024
Moving Bucket Data Between Storage Providers
In some cases, it might be necessary to transfer storage bucket data from one provider to another.
The following procedure covers scenarios where you currently rely on FileSystem as a storage provider and want to move to Orchestrator, provided that its configured storage type is FileSystem. For convenience, we will refer to FileSystem as source and to Orchestrator as destination.