In three straightforward steps, batch upload your legacy contracts and metadata to your Juro repository.
Learn how to bulk upload documents and run AI Extract here.
💡 NOTE: This feature is available for PDF files.
You can set the status of the contracts in a bulk upload as:
UPLOADED: these can be updated to fully signed, or
FULLY SIGNED: these documents are locked to all further changes, but you can still create new smartfields for data-keeping purposes.
The Bulk Upload feature doesn't support password-protected documents.
What can Juro's Bulk upload feature do? 🧐
Contracts created in Juro include information captured through smartfields and stakeholder input, which is then reflected in each contract's timeline.
Your legacy documents also contain important data. Uploading them to Juro improves accessibility to them and also ensures they're securely stored.
Individual PDF uploads with no existing metadata can be uploaded on the Documents homepage.
When you upload a file against one of your template structures, it replaces the document body while applying the template's data structure, such as smartfields and stakeholder information.
For example, if you select a template with smartfields X, Y, and Z, your uploaded document will maintain these so you can capture and store information from your uploaded contract using AI Extract.
If you already have a spreadsheet containing important document metadata, the steps below outline how to upload your PDF files in bulk and auto-populate smartfields with your spreadsheet data. Alternatively, you can use Juro's sample template as your starting point - this is explained below in more detail.
What about importing individual documents? 📄
Individual PDF uploads with no existing metadata can be uploaded on the Documents homepage.
With individual uploads, users must populate the smartfields on each document.
Step 1️⃣ : Create a template with the related smartfields 🏗️
To get started:
1. In Juro, add the relevant smartfields to your template: you can leave these empty for now. |
|
The names of these fields should match the header columns of your CSV file (e.g. 'Effective Date'. You should also select the relevant smartfield type for the data. |
💡 NOTE: If you wish to mark your uploaded files with the FULLY SIGNED status and/or run them through AI Extract, leave the approvers and signatories columns of your CSV file empty.
2. Republish your template. |
|
Step 2️⃣ : Start the upload flow ⬆️
Before beginning this step:
Configure your CSV columns: ensure your CSV file includes columns for the data points you need. Only data in matching visible columns will be imported into your smartfields
Check all data (including formatting): Verify data accuracy for all cells. This includes:
Ensuring your data is correct
Confirming that the format of your cell inputs matches the Juro smartfield format type (e.g. if a Juro calendar field is DD/MM/YYYY, the cell input on your CSV must match this). Then:
1. From your Workflows page, click Bulk actions.
Then, on the New bulk actions page, under Bulk upload, select Browse to add files. |
|
You can now select the documents to be uploaded from your desktop. |
2. Select the Juro template you created earlier. On the next page, click Sample: this exports Juro's bulk upload template, which automatically contains your template's smartfields as columns. |
|
Step 3️⃣ : Fill in and re-upload your CSV 📄
In Juro’s sample CSV template:
Each column corresponds to the smartfields in your template
Each row represents a document that will be uploaded
Each cell is the data that will be input into the smartfields
Additionally, the sample template has the following mandatory columns. These must be present and populated correctly for the import to work:
File name | This column populates automatically during Step 1 of the initial upload flow. |
Document name
| This is the name you’d like the document to have in Juro. |
Status
| This input is case-sensitive and must be either Fully signed or Uploaded.
If you plan to use AI Extract on uploaded documents, the status must be set to Uploaded. |
Document owner
| The email address of the person who will own this document in Juro. |
Signing side #2
| This names the first counterparty on the upload contract. |
Populate the relevant cells and leave the ones you don't need empty. You can leave the signatory, approver and recipient email columns blank, as these are for documents you intend to share externally through Juro.
When you're ready, save your CSV file. Then:
1. Back in Juro, click Upload CSV and select the CSV template from your desktop. |
|
Review the import for errors (some troubleshooting tips here).
|
2. Complete the upload by clicking Upload X documents. You'll be directed back to the bulk actions page, where you can view the upload. |
|
If something has gone wrong, you can amend the CSV and use the Re-import CSV button to upload the corrected data. |
Setting parent/child relationships in advance 🧑🧑🧒🧒
In the Related documents tab of each contract record, your users can group contracts and assign them as a parent or child document.
Juro's sample CSV includes Parent and Relationship type columns you can use to complete this process before importing your files.
Post-upload, this data from these columns shows in each imported contract record's Related documents sidebar. It's also retrievable from a View by adding the above columns.
To do this:
1. Start the bulk upload process by selecting your documents and preferred template to define your data fields. Then, export the sample CSV provided. |
|
2. Enter the row number of the parent column into the Parent document cell of the child contract's row*. If the document is already in Juro, input the document's ID (the string of letters/numbers after app.juro.com in your browser's address bar when viewing the contract).
Amendment: when a document actively amends your parent agreement (i.e. changes what it says).
Related document: when a document doesn't amend the parent agreement, but may be helpful to reference in the future. |
|
*💡NOTE: Row 1 in the sample CSV contains header information, with your documents beginning from row 2. The header row must be in place for a successful upload.
** Where there is no parent document, this cell should be left blank. |
When you re-upload the CSV, you should see the following outcomes:
The document relationships you've defined in your CSV will now show in the Related documents sidebar of the relevant contracts.
Your child document will show in the Children column of the parent contract's row. Learn more about adding these columns here.
Troubleshooting errors 🔨
CSV files are sensitive to the data input. Where its columns don't match the parameters of the linked Juro field, the platform will generate an error.
These errors show on the final upload page: scrolling across, you'll see an ! icon next to any problem cells/columns. When you hover over this, Juro shows a recommendation to fix the issue in the source CSV file.
Occasionally, you may see an error saying that your CSV doesn't match Juro's bulk upload requirements. To see a list of any errors, click the errors here link:
Finally, here are some additional questions to help you to troubleshoot errors during the bulk upload process.
Are all of your cell inputs in the correct format?
A common error we see with CSVs relates to date and number fields. Any CSV inputs that don't match the format of the Date & Number Region field in your Workspace settings will trigger an error. Similarly, CSV columns linked to a Choice smartfield must have inputs that match exactly an option in the Juro smartfield.
Does the data in your File Name column match the file name exactly (including capitalisation and file extension)?
You should also check individual cells and the file name on your desktop for accidental spaces added at the beginning or end of the file name.
Do the relevant stakeholders have access to the Juro template you're using?
Internal signatories, approvers and contract owners* must be in a group with access to the template you're using.
*If they don't, ownership is assigned to the user uploading the documents.
Any signatories set on your template will be removed from contracts uploaded with the FULLY SIGNED status. On the confirmation screen, these documents display a yellow question mark icon and are listed in a separate Notices tab.
Managing special characters 🔣
CSV files with special characters (e.g. !, @, #) must be saved as a UTF-8 file.
Managing special characters from Excel
Download your CSV samples to your desktop. Then:
1. Beginning with a blank Excel workbook, go to the Data tab and select Get Data, then click From Text/CSV and select the Juro CSV sample.
2. In the import dialog, set the File Origin to 65001: Unicode (UTF-8) so Excel reads the special characters correctly.
3. Delimit your Excel file: Select Delimited > Next, check the Semicolon and Comma delimiters and click Finish.
4. In the Import Data pop-up, leave the default value unchanged and press OK.
Managing special characters from Numbers (Mac users)
Download your CSV samples to your desktop. Then:
1. Click File > Export to > CSV. From the Text Encoding dropdown, select Unicode (UTF-8).
2. Select Next and specify the file destination.
Managing special characters from Google Sheets
If Excel continues to cause issues with special characters:
1. Open the CSV in Google Sheets (which handles UTF-8 natively).
2. Make your edits and download as CSV via File > Download > Comma-separated values (.csv): Google Sheets always exports as UTF-8.
3. Re-upload to Juro.
The bulk upload flow process is the same across your Juro environment: simply repeat the above steps in the relevant workspace.
You can learn more about troubleshooting your CSV import in our dedicated article.
💁♀️ As always, our Support Team is happy to help you with anything further if needed. Start a chat with us right here by clicking the Intercom button in the bottom-right-hand corner of this page.
Alternatively, you can email us at support@juro.com 🚀