---
sourceDocument: Brazil Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/integrate-applications

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Upload an automation package attachment

# Upload an automation package attachment in RPA Hub {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Upload a zip file of the automation package in RPA Hub to manually migrate the package from a lower (non-production) to a higher (production) environment.

## Before you begin

You must do this task in the classic environment.

Ensure that you've completed the tasks that are related to migrating your data from a
lower environment to a higher environment. For more information, see [Migrating your data from a lower environment to a higher environment in RPA Hub](https://www.servicenow.com/docs/~Gnhskj3_22Rndj8pp2Zag "As a system administrator, after you restructure the RPA Hub tables to extend the Application file (sys_metadata), you can use the update set capability to migrate your data from a lower (non-production) environment to a higher (production) environment for real-time use.").

Download the package version attachment from a lower instance. For more information,
see [Download a package version in RPA Hub](https://www.servicenow.com/docs/~A6xJlMkERRK7roEw6PqaQ "Download a package version in RPA Hub so that it can be opened from the RPA Desktop Design Studio to build, debug, or modify the automation.").

Ensure that the
sn_rpa_fdn.allow_manual_upload_of_automation_package system
property is marked as true. If you have the admin role, you can edit this system
property.

Verify that the life-cycle stage of the package version isn't set to
Retired.

Ensure that there's no valid attachment that is associated with the package version
record.

For a quick integrity check, verify that the HashCode of a package version is correct. If the validation fails, remove the incorrect attachment that you previously uploaded by selecting Manage Attachments.
Then, proceed with this task to upload a correct attachment. For more information about verifying the HashCode, see [Verify the HashCode of a package version in RPA Hub](https://www.servicenow.com/docs/zdSfLHhNxIauHu3xjIgusg "Verify the HashCode of a package version in RPA Hub so that you can validate the HashCode of the manually uploaded automation zip file with the associated package version record.").

Role required: sn_rpa_fdn.rpa_release_manager

## About this task

You can upload the valid attachment only one time. The Upload Attachment button to upload attachments is turned off after you upload a valid attachment.

## Procedure

1. Navigate to AllRobotic Process AutomationBuildPackages.
2. Open a package that you want to upload a package version for.
3. On the Package Versions tab, select a version.
4. In the form header, select Upload Attachment to upload a zip file of the automation package.
5. In the Confirmation dialog box, select Choose file.

## What to do next

For a quick integrity check, verify the HashCode of a package version again. For more information, see [Verify the HashCode of a package version in RPA Hub](https://www.servicenow.com/docs/zdSfLHhNxIauHu3xjIgusg "Verify the HashCode of a package version in RPA Hub so that you can validate the HashCode of the manually uploaded automation zip file with the associated package version record.").

*[\>]: and then