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

WhatWhereFileChecked before saving
Controls, policies and evidence from another platform (Vanta, Drata or any export)Import in the sidebarControls as CSV or Excel (.xlsx), up to 1,000 rows; optional ZIPs of policies and evidenceYes: you review every row and untick what should not count
Your existing policy documentsPolicies, Import policiesPDF, Word (.docx), text or Markdown; up to 40 files of 25 MB eachYes: one table to review before the policies are created
Access register lines (who has access to which system)Access Reviews, Register, Import CSVCSV or Excel (.xlsx) built from the template; up to 1,000 rowsYes: each row is marked valid, duplicate or in error as soon as you choose the file
An access list from a screenshot or a PDFInside the Import CSV dialog: Read a screenshot or PDFPNG, JPEG or WebP up to 7 MB, or a PDF up to 10 MBYes: you tick the accounts to add
Your people directory (an HR list)Access Reviews, Register, People, Import peopleCSV or Excel (.xlsx); up to 5,000 rowsYes: Check the file shows what will be added, updated and marked as leavers
Key risk indicators with thresholds and historyRisk Management, KRIs, Import ExcelTwo Excel workbooks (.xlsx): thresholds and monthly valuesNo. 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 functionsDORA, Register of Information, Import CSVOne CSV file per record typeNo: rows are saved one by one, and the first 50 problem rows are listed
A security questionnaire you receivedThird-Party Risk, Questionnaires, New questionnaireExcel (.xlsx, .xlsm), CSV, Word (.docx) or text; up to 5 MB and 1,000 questionsNo: 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

ImportPlanPermission
From another platformProfessional, EnterpriseManage for Import (administrators by default)
Policy documentsBasic, Professional, EnterpriseEdit for Policies (administrators and editors)
Access register lines from CSV or ExcelEvery plan, including FreeEdit for Access Reviews (administrators and editors)
Access list from a screenshot or PDFProfessional, Enterprise: it uses your own AI key, which can be saved on those plansEdit for Access Reviews (administrators and editors)
People directoryEvery plan, including FreeManage for Access Reviews (administrators by default)
KRIs from ExcelProfessional, EnterpriseManage for GRC (administrators by default)
DORA register CSVProfessional, Enterprise, with DORA enabledManage for Register of Information (administrators by default)
Questionnaire you receivedBasic, Professional, EnterpriseEdit 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:

RegisterHow records get in
Risk register, ICT assetsAdded 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.
ControlsEach 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.
EvidenceAttached on each control, or brought over in one go as the evidence ZIP of Import.
Tasks, incidents, change requestsCreated in the app.
UsersInvited 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 recordsRecorded 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.

WhereFiles per upload
Evidence on a controlSeveral at once; each becomes its own evidence item
Documents on a policyOne
Documents on an ICT provider or on a contractOne
Attachments on an incident or a change recordOne
Supporting files on a KRI measurementOne
The evidence request page, for people without a loginOne 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.