If you're moving to ComplyJet from Vanta, Drata, or a similar platform, the good news is that a previous SOC 2 (or ISO 27001) report doesn't get thrown away — it's proof your controls already work, and your auditor relationship and control design generally carry over conceptually even though the tooling is changing.
What carries over automatically
Your actual infrastructure, integrations, and controls don't change just because the platform managing them does. When you connect your existing AWS/GCP/GitHub/HR tools to ComplyJet, it evaluates the real state of those systems — so if you were genuinely compliant on your previous platform, you should see most tests pass quickly once integrations are reconnected, rather than needing to rebuild your security posture from scratch.
Migrating your data
ComplyJet supports one-click migration for Vanta and Drata — connect your existing account and we'll pull your data across for you. For any other platform, the path depends on what your provider offers: if they have an API, our support team uses it to fully migrate your data on your behalf; if they don't, you'll need to do a manual data export, and our support team will help you import it into ComplyJet. A few things to expect either way:
Policies need to be re-created or re-uploaded — ComplyJet's AI policy generator can draft them quickly from your existing policy text as a starting point rather than from scratch, but this isn't a fully automatic import.
Your previous audit report itself is worth keeping and uploading as a document — it's useful evidence of your compliance history, and can be added to your Trust Center resources so prospects still see continuity even while you're mid-transition.
Your milestone/readiness status (e.g. "SOC 2 Type I complete") isn't something ComplyJet infers from your prior platform — if your dashboard shows Type I readiness tasks even though you're already Type II-compliant elsewhere, that's expected until it's set correctly for your account; reach out to support to get your milestones reflecting where you actually are, rather than working through onboarding tasks you've already completed elsewhere.
The practical first step
Reach out to support (or your onboarding contact, if you have one) and mention you're switching from another platform specifically — there's enough nuance in what should and shouldn't be treated as "already done" that this is worth a conversation rather than working through the default onboarding flow blind.