Buying GRC

How do I migrate from Vanta or Drata to Keel?

Short answer

You can move your program to Keel with keel-migrate, our open-source tool. It exports your vendors, risks and people, plus your policies wherever it can read them, into an open format that you then import into Keel. From Vanta and Hyperproof it also brings your evidence files. Policy documents from Vanta and Hyperproof arrive as links rather than files, and policies from Drata arrive without their documents, so export those by hand. Large exports are split across files automatically. The tool reads Vanta, Drata, Hyperproof, Oneleet and Secureframe today, with OneTrust in beta.

Last updated

Step by step

  1. Export with keel-migrate. Run the open-source keel-migrate tool against your current platform. It writes your records, and any document files the platform’s API serves for download, into an open format.
  2. Review the exported files. The export is plain, open data you can inspect and keep; large libraries are split across multiple files automatically.
  3. Import into Keel. Upload the exported bundle to your Keel workspace. It brings in whatever records and files the export captured from your platform.
  4. Re-map to your frameworks. Imported files arrive in your evidence library without links to controls. Attach each one to the Keel control it supports, and because Keel is crosswalk-native, it then counts toward every framework that control satisfies.

What comes across

keel-migrate exports your vendors, risks and people, plus your policies wherever it can read them. Secureframe sends vendors, risks and people only. OneTrust (in beta) sends risks and people only. The tool also pulls the document files themselves where the API serves them for download. Today that covers evidence from Vanta and Hyperproof, and Oneleet policy documents when served from that platform’s own API. Policies without a downloadable file arrive as records, carrying their document link where the platform provides one. Evidence the tool cannot download is not exported, so export it by hand. Risks from Secureframe and OneTrust carry no likelihood or impact scores, so they arrive unscored and you score them in Keel.

Open format, no lock-in

The tool is open source and exports to an open format, so your compliance data is yours to keep and move. That is the point: switching platforms should not mean abandoning the evidence you have already collected.

Where Keel fits

Once imported, your program lives on Keel’s single crosswalked control-and-evidence graph, so a control you implemented once counts toward every framework it satisfies. keel-migrate reads Vanta, Drata, Hyperproof, Oneleet and Secureframe today, with OneTrust in beta, and more sources are planned.

FAQ

Does migration move my evidence files, or just records?

That depends on the platform. Evidence from Vanta and Hyperproof comes across as the files themselves. keel-migrate does not pull evidence files from Drata, Oneleet, Secureframe or OneTrust, so export that evidence by hand before you leave.

Which platforms can I migrate from?

Vanta, Drata, Hyperproof, Oneleet and Secureframe today, with OneTrust in beta. More source platforms are planned, and because the export is an open format, your data is portable regardless.

Next step

Get audit-ready with Keel

The AI-native GRC platform for SMBs: one control-and-evidence graph across SOC 2, ISO 27001, HIPAA, PCI DSS, NIST CSF, and more. Start free, no credit card.