You rarely start from nothing. Controls live in another platform, policies in a shared folder, access lists in spreadsheets, KRIs in Excel. This page lists every way to bring existing records into Venvera from a file, where to find each one, what the file must look like and who can run it, with a link to the full guide for each.
What you can import
| What | Where | File | Checked before saving |
|---|---|---|---|
| Controls, policies and evidence from another platform (Vanta, Drata or any export) | Import in the sidebar | Controls as CSV or Excel (.xlsx), up to 1,000 rows; optional ZIPs of policies and evidence | Yes: you review every row and untick what should not count |
| Your existing policy documents | Policies, Import policies | PDF, Word (.docx), text or Markdown; up to 40 files of 25 MB each | Yes: one table to review before the policies are created |
| Access register lines (who has access to which system) | Access Reviews, Register, Import CSV | CSV or Excel (.xlsx) built from the template; up to 1,000 rows | Yes: each row is marked valid, duplicate or in error as soon as you choose the file |
| An access list from a screenshot or a PDF | Inside the Import CSV dialog: Read a screenshot or PDF | PNG, JPEG or WebP up to 7 MB, or a PDF up to 10 MB | Yes: you tick the accounts to add |
| Your people directory (an HR list) | Access Reviews, Register, People, Import people | CSV or Excel (.xlsx); up to 5,000 rows | Yes: Check the file shows what will be added, updated and marked as leavers |
| Key risk indicators with thresholds and history | Risk Management, KRIs, Import Excel | Two Excel workbooks (.xlsx): thresholds and monthly values | No. Rows that cannot be read are left out and the rest is saved; a missing legal entity or overlapping bands stop the import and nothing is saved |
| DORA register: ICT providers, contracts and business functions | DORA, Register of Information, Import CSV | One CSV file per record type | No: rows are saved one by one, and the first 50 problem rows are listed |
| A security questionnaire you received | Third-Party Risk, Questionnaires, New questionnaire | Excel (.xlsx, .xlsm), CSV, Word (.docx) or text; up to 5 MB and 1,000 questions | No: check the question count after the upload |
Accounts can also be read straight from Microsoft Entra ID or Google Workspace, without a file: see Discover from directory in Access Reviews.
Plans and permissions
| Import | Plan | Permission |
|---|---|---|
| From another platform | Professional, Enterprise | Manage for Import (administrators by default) |
| Policy documents | Basic, Professional, Enterprise | Edit for Policies (administrators and editors) |
| Access register lines from CSV or Excel | Every plan, including Free | Edit for Access Reviews (administrators and editors) |
| Access list from a screenshot or PDF | Professional, Enterprise: it uses your own AI key, which can be saved on those plans | Edit for Access Reviews (administrators and editors) |
| People directory | Every plan, including Free | Manage for Access Reviews (administrators by default) |
| KRIs from Excel | Professional, Enterprise | Manage for GRC (administrators by default) |
| DORA register CSV | Professional, Enterprise, with DORA enabled | Manage for Register of Information (administrators by default) |
| Questionnaire you received | Basic, Professional, Enterprise | Edit for Inbound Questionnaires (administrators and editors) |
An administrator can give any of these permissions to a single user in that user's permissions under Settings. See Understanding roles and permissions.
Preparing a file
- Excel: save as .xlsx. Old .xls workbooks are not read. Only the first worksheet is used, except for the KRI values workbook, where you name the worksheet.
- CSV: save as UTF-8 with commas between the values. The DORA register and the questionnaire upload also read semicolons.
- Header row: the first row holds the column headings. The guide for each import lists the headings it recognises. The two KRI workbooks are the exception: they are read by column position, and the thresholds workbook has a title row above its headings.
- Dates: write them as year, month, day: 2026-01-31.
- Names must match exactly. A system, a legal entity or a provider named in a file is looked up under that name in Venvera. A different spelling is not found: the row is refused, and for a legal entity the whole KRI import stops. Provider names ignore capital letters; system and legal entity names do not.
- Import each file once. Most imports add records without checking whether the same record came in before. Where an import does recognise existing records (people by e-mail or employee number, access lines by person and system, providers by LEI, KRIs by legal entity and name), the guide says so.
- Start small. Where there is no review step, import a file of five rows first and look at the result before you load the rest.
What cannot be imported from a file
These registers have no file import today. Records are added in the app:
| Register | How records get in |
|---|---|
| Risk register, ICT assets | Added one at a time. On the Professional and Enterprise plans, Set up with AI drafts your first risks, KRIs, third parties and ICT assets from ten questions. |
| Vendors (ICT providers) | Added one at a time under Third-Party Risk, ICT Providers. Organisations with DORA enabled can load them through the Register of Information CSV import; they then appear in both places. |
| Controls | Each framework brings its own controls when you enable it. Controls from another platform are matched to them by Import; controls that match nothing are not created. |
| Evidence | Attached on each control, or brought over in one go as the evidence ZIP of Import. |
| Tasks, incidents, change requests | Created in the app. |
| Users | Invited one by one under Settings; see User management. People who only appear in access reviews are not users and are loaded with the people import. |
| Training records | Recorded when people take a training in Venvera. Completions from another learning system cannot be loaded. |
The public API reads data; it does not create records.
Attaching files to a record
Attaching a file is different from importing one: the file is stored with the record as it is, and its contents are not read into any register.
| Where | Files per upload |
|---|---|
| Evidence on a control | Several at once; each becomes its own evidence item |
| Documents on a policy | One |
| Documents on an ICT provider or on a contract | One |
| Attachments on an incident or a change record | One |
| Supporting files on a KRI measurement | One |
| The evidence request page, for people without a login | One per requested item |
- File types: PDF, Word, Excel, CSV, text, PNG and JPEG. Documents on a provider or a contract take .docx and .xlsx, not the older .doc and .xls.
- Size: 25 MB per file. When several files are sent together they must total under 25 MB.
- Checked on arrival: the content of a PDF, an image or an Office file has to match its type, so a renamed file is refused.
- Stored encrypted with your organisation's own key.
Data that arrives without a file
- Integrations. The Microsoft Azure, Google Workspace and AWS connections run security checks and collect evidence from your own accounts.
- Directory discovery. Access Reviews can read who is able to sign in to Microsoft Entra ID or Google Workspace and propose the register lines to add.
- E-mailed links. People without a login can send you evidence, report a KRI value, answer a vendor questionnaire or take a training through a personal link. What they submit lands on the record it was requested for.