Transfer engagements in bulk with CloudBridge

Use CloudBridge to transfer data from multiple Working Papers engagements to Cloud. If you haven't installed CloudBridge, see Get CloudBridge.

These instructions only apply to CloudBridge (All regions, Bulk). For individual transfer instructions, see Transfer individual engagements with CloudBridge.

Best practices

Before you get started, we recommend performing the following best practices, based on your environment:

Environment Best practices
Desktop / On-premises
  1. Create (or import) any required entities.

  2. Organize the files on your local or network drive, for example:

    • alphabetically

    • by file type

    • by priority

    • by product

    • by upload sequence

    We recommend using Caseware Tracker as an efficient way to achieve this.

  3. Use Caseware Tracker to move any external files out of the engagement file folder to a backup location. Since CloudBridge only transfers the engagement file itself, moving these external files reduces the transfer process time.

Hybrid Cloud
  1. Using the Caseware Batch Tool, create local sync copies of your Cloud engagements (To configure the Batch Tool: Step 3).

  2. Organize the files on your local or network drive. for example:

    • alphabetically

    • by file type

    • by priority

    • by product

    • by upload sequence

  3. After performing the setup and transfer procedures below, use the Caseware Batch Tool to delete the local sync copies (To configure the Batch Tool: Step 4).

Additionally, we recommend that you:

  • Close any other applications while running CloudBridge.

  • Run Cloudbridge overnight or during off-hours.

  • Limit each upload to 500 engagements at a time.

Set up CloudBridge

After you’ve installed CloudBridge, you’ll need to connect to the destination Cloud site where the engagement data will be transferred.

To set up CloudBridge:

  1. Launch CloudBridge.

  2. In the Edit servers dialog, enter the name and URL of the destination Cloud site where the engagement data will be transferred. You can add more Cloud sites by selecting Add a server, but note that data can only be transferred to one app in one Cloud site at a time. When finished, select Done.

  3. From the Server drop-down menu, select the applicable Cloud site and select Connect.

  4. The login prompt is displayed. Enter your credentials and select Sign-in to connect to the Cloud site.

Transfer engagement data

Once you’ve connected CloudBridge to your destination Cloud site, you’re ready to begin transferring engagement data.

Note: Accounts with zero balances will not be transferred. If you require zero-balance accounts in a destination Cloud engagement, you must manually add and assign them.

To transfer engagement data:

  1. On the CloudBridge main menu, select New upload.

  2. On the General step:

    1. Enter a name for the transfer.

    2. Select the application where you’ll work with the transferred engagement data. Note that if you need to work with the data in another app, you must perform an additional, separate transfer.

    3. Select Next.

  3. On the Source file settings step:

    1. Specify the directory of the source Working Papers engagements with the data you want to transfer.

    2. (Optional) Filter the source Working Papers engagements by entering a start and end date. Only data from engagements within the range will be transferred.

    3. Select the applicable data points to transfer. The options include adjustments, general ledger, trial balance (multiple years), external documents/folders and risks and controls.

    4. If you select Trial balance (multiple years), you have the option to use a custom mapping file.

      To create a custom mapping file, contact your local distributor or Caseware representative.

      To use a custom mapping file, complete the following requirements:

      • Ensure the mapping file follows the naming convention <Product Name>.ini, where <Product Name> matches the product name on the General step.

        For example:

        • Caseware ReviewComp.ini

        • OnPoint Audit.ini

        • Audit International.ini

      • Move the remap file to C:\Users\Public\CloudBridge.

      • In CloudBridge, select Use custom mapping file.

        Note: If CloudBridge reports “No mapping file found”, verify that the remap file name and location are accurate.

    5. Select the applicable external files to transfer. The options include Word, Excel, PowerPoint, PDF, CSV, Text, JPG, PNG or all external files.

    6. Select Next.

  4. On the Cloud file settings step:

    1. Select a naming method for new engagements created using the transferred data. The options include Working Papers file name, operating name and Cloud entity.

    2. Select a year end date format to include in the name for new engagements.

    3. Select whether to include the year end date, or place it at the beginning (prefix) or end (suffix) of new engagement names.

    4. Select Next.

  5. On the Files to upload step:

    1. Select the Cloud entity where you want to transfer the data (for each source file).

    2. Select the Cloud engagement where you want to transfer the data (for each source file). If no Cloud engagement is selected, a new engagement will be made in the selected entity.

    3. Select Next.

  6. On the Upload settings step:

    1. Specify the maximum duration of the transfer. The options include 1, 2, 3 and 4 hours. After the duration has elapsed, CloudBridge will close, even if the transfer is incomplete.

    2. Specify the timeout for each source engagement. The options include 5, 10, 15 and 20 minutes. After the duration has elapsed, the transfer will skip to the next source engagement, even if the previous is incomplete.

    3. Select Next.

  7. On the Summary step:

    1. Review all the settings you’ve selected. If you need to make additional changes, select Previous.

    2. Select Upload Files.

The engagement data transfer begins. You’ll see the status of your transfer as it progresses and a final report when complete.

Notes:

  • If any transfers failed, you can select More actions () | Rerun to retry the transfer for that specific file.

  • After the transfer is complete, Hybrid Cloud users should delete their local sync copies using the Caseware Batch Tool (To configure the Batch Tool: Step 4).

  • To perform another transfer, restart this procedure.