Free tools Windows power users keep installed
One-click scans. No signup required.
Before moving UiPath to Automation Cloud, export any robot logs and audit records you may need later, then configure tenant-level robot-log export to Azure, AWS S3, or Google Cloud Storage for ongoing retention. Automation Cloud keeps several kinds of records in separate stores with separate retention policies, so migrating the service does not by itself preserve every historical log or execution record.
Know which UiPath records you need to retain
“Logs” can mean different records in UiPath. Robot execution logs contain messages generated during automation runs. Audit records capture administrative and service activity. Jobs, queue items, execution records, and execution media are governed by Process Data Retention. Treat each category as a separate retention requirement.
| Record type | What it covers | Where to plan for it |
|---|---|---|
| Robot execution logs | Messages generated during robot executions | Orchestrator folder-level Logs experience; configure tenant-level export for ongoing retention. UiPath says Orchestrator keeps robot logs for a maximum of 31 days (About logs). |
| Audit records | Administrative and service activity | Audit experience and its searchable or archived records; its export options and periods differ from robot logs (Orchestrator Audit). |
| Process data | Jobs, queue data, execution records, and execution media | Process Data Retention Policy. This policy is configured and applied independently from Robot Log Retention (Process Data Retention Policy). |
Decide which of these records your troubleshooting, compliance, or operational policies require before planning the move. Retaining robot logs alone does not preserve audit history or process data.
What happens to logs during migration
UiPath documents robot execution logs as retained for 30 days during organization data moves. Separately, its Automation Cloud documentation says Orchestrator keeps robot logs for a maximum of 31 days. These are bounded retention periods, not a long-term archive; export records before migration if you need historical evidence or troubleshooting data (Managing organization settings; About logs).
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →#1 Best Overall
- Robotic Process Automation using UiPath StudioX: A Citizen Developer’s Guide to Hyperautomation
- ABIS BOOK
- Apress
Do not assume that enabling export in the destination tenant will recover logs that have already aged out. UiPath states that the robot-log export configuration does not backfill the preceding 30 days of logs (Exporting logs).
Retention and export options by record type
| Records | Availability or export scope | Important distinction |
|---|---|---|
| Orchestrator robot logs | Kept for a maximum of 31 days | Tenant-level export supports Azure, AWS S3, and Google Cloud Storage; configuration does not backfill the prior 30 days. Source: About logs and Exporting logs. |
| Orchestrator audit data | Searchable for at least six months, with monthly archives covering the preceding 18 months—24 months of total availability under the documented policy | Archived records are not the same as records in the searchable period. Source: Orchestrator Audit. |
| Unified Audit UI export | Up to 100,000 logs from the last 90 days | This is the documented UI CSV export scope, not a promise of an unlimited export. Source: About logs. |
| Long-term audit export | Up to five years for Enterprise plans and two years for other plans | Plan eligibility affects the export period. Source: About logs. |
| Jobs, queue data, execution records, and execution media | Duration depends on the configured Process Data Retention Policy | This is configured separately from robot-log retention. Source: Process Data Retention Policy. |
Migration runbook: preserve history and verify the new setup
- Inventory the records and destinations. List robot execution logs, audit records, job and queue data, execution media, and any feed to an external SIEM or archive. Note which records are required for troubleshooting, compliance, or analysis.
- Export legacy robot logs and audit records before the move. Keep the exported files with their UTC time range and tenant and folder identifiers so you can identify their origin and scope later. Do not rely on the destination export configuration to backfill prior robot logs.
- Check access in the target tenant. Confirm folder permissions for operators who need the Logs page, and tenant or administrator permissions for users responsible for Audit and export configuration. UiPath’s About logs and Exporting logs documentation describe the relevant experiences and export setup.
- Configure robot-log export before production cutover. Choose Azure, AWS S3, or Google Cloud Storage and follow UiPath’s export procedure. Verify that newly generated entries arrive at the destination; this tests ongoing delivery, not historical backfill.
- Set process-data retention separately. Review the Process Data Retention Policy for jobs, queue data, execution records, and media. If policy requires a longer retention period, plan the appropriate Orchestrator or external storage archive for those records instead of assuming robot-log export covers them.
- Validate a representative job end to end. Locate its execution logs, check that the job ID and process version are present, confirm that the new log entries reached the export destination, and record who owns retention for each copy. This operational check helps expose access or delivery gaps while the migration can still be corrected.
Choose an export destination and retention policy
UiPath supports Azure, AWS S3, and Google Cloud Storage as robot-log export destinations. The right choice depends on where your organization already manages access, retention, compliance, and analysis; the available UiPath documentation establishes these destination categories but does not establish a universal best option.
- Retention and lifecycle: Set a retention period that meets your operational and compliance needs, and decide whether older files should move to a lower-cost storage tier or expire.
- Access and security: Limit who can read or change the archive, and evaluate the encryption controls available in your selected storage service.
- Region and compliance: Confirm that the storage region and handling rules meet applicable residency and compliance requirements.
- Analysis and correlation: Make sure your archive or BI/SIEM workflow can use useful log fields such as job ID, process name, and process version to connect entries to executions.
- Cost: Account for retained volume, storage tier, retrieval, and any analysis or transfer charges under your organization’s provider terms.
Set diagnostic detail without exposing unnecessary data
Orchestrator supports Trace, Debug, Info, Warn, Error, and Fatal logging levels (Logging Levels). Use the lowest level that provides useful routine production diagnostics, then raise detail for a bounded troubleshooting window and return to the baseline when the investigation ends.
When reviewing what your workflows log, consider whether variable or argument values could reveal sensitive information. UiPath’s logging guidance identifies fields including Message, Level, Timestamp, jobId, processName, processVersion, windowsIdentity, and robotName (Logging Levels). Preserve the identifiers needed to investigate a run, while limiting sensitive values and controlling access to exported records.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Plan for three separate retention owners
A reliable post-migration setup assigns an owner and policy to each record store: robot logs in Orchestrator and the configured export destination, audit records in the Audit experience and its archives or exports, and process data under the separate Process Data Retention Policy. Documenting the retention period, access owner, storage location, and a job-correlation method for each prevents a successful robot-log export from being mistaken for a complete record of the automation estate.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
