The VP HR at a 600-person IT services company in Pune had been unhappy with their BGV vendor for 18 months. Amber rates above 12%. TAT averaging 14 days for employment checks. An “account manager” who responded to emails approximately never. But every time she raised switching, the same objection came back from her team: “Migration will be a nightmare. Let’s just push them harder.”<\/p>\n\n\n\n
She finally switched. It took 6 weeks. The nightmare never materialized.<\/p>\n\n\n\n
Don’t switch because a competitor’s sales rep had better slides. Switch when measurable problems persist:<\/p>\n\n\n\n
\u2022Amber rate above 10% for two consecutive quarters<\/p>\n\n\n\n
\u2022TAT SLAs missed by more than 20% consistently<\/p>\n\n\n\n
\u2022No integration with your current HRMS (Darwinbox, Keka, Zoho People, GreytHR)<\/p>\n\n\n\n
\u2022Pricing has crept up through surcharges (address verification extras in places like Gorakhpur or Siliguri, priority fees, re-verification charges) that weren’t in the original contract<\/p>\n\n\n\n
\u2022Legal team has flagged DPDPA data handling concerns the vendor won’t address<\/p>\n\n\n\n
\u2022Account management responsiveness has degraded below acceptable standards<\/p>\n\n\n\n
If three or more apply, you have a vendor problem, not a bad quarter.<\/p>\n\n\n\n
1. Document current state.<\/strong> Export from your current vendor: check packages by role tier, TAT benchmarks by check type, cost per check (including all surcharges), amber rates by check type and geography, current integration setup with your HRMS, and volume data (monthly check count by type).<\/p>\n\n\n\n 2. Extract pending cases.<\/strong> Get a complete status report for every in-progress verification. These will need to be completed by the old vendor even after you transition.<\/p>\n\n\n\n 3. Review your contract.<\/strong> Most BGV contracts have 30-60 day notice periods. Check for: minimum volume commitments (and penalties for under-delivery), auto-renewal clauses, data deletion obligations upon termination, and intellectual property provisions around custom workflows.<\/p>\n\n\n\n 4. Configure check packages.<\/strong> Replicate your exact tier structure on the new platform. Don’t “optimize” packages during migration \u2014 change one thing at a time.<\/p>\n\n\n\n 5. Integration testing.<\/strong> Connect your Darwinbox\/Keka\/Zoho People instance to the new vendor. Run 3-5 dummy candidates through the full workflow. Test: check initiation from inside your HRMS, candidate notification and document collection, result delivery back into your HRMS, and report generation and download.<\/p>\n\n\n\n 6. Migrate consent templates.<\/strong> Your DPDPA-compliant consent form must work in the new vendor’s system. Review with Legal \u2014 consent language may need minor adjustments.<\/p>\n\n\n\n 7. Map escalation contacts.<\/strong> Know exactly who to call when something goes wrong. Get mobile numbers, not just email addresses. For your first 30 days, you need a direct line to someone senior.<\/p>\n\n\n\n 8. Run 25-30 real checks through both vendors simultaneously.<\/strong> This is the most important step. Pick candidates that represent your actual mix: 60% metro, 25% tier-2, 15% tier-3\/rural. Compare side by side: TAT, report quality, amber rate, candidate experience (ask candidates which process was smoother), and fully-loaded cost.<\/p>\n\n\n\n 9. Team evaluation.<\/strong> Have your TA team and HRBPs compare both dashboards. Usability matters more than features. The platform your team finds intuitive wins.<\/p>\n\n\n\n 10. Legal review.<\/strong> Your General Counsel reviews: new vendor’s data processing agreement, subprocessor list, consent workflow compliance, and data breach notification commitments.<\/p>\n\n\n\n 11. Full transition.<\/strong> All new checks go to the new vendor. Keep the old vendor active only for cases still pending from the parallel period.<\/p>\n\n\n\n 12. 30-day post-cutover review.<\/strong> Compare first month on new vendor against last month on old vendor: TAT (by check type), amber rate, team satisfaction (NPS survey), candidate feedback, and actual vs projected cost.<\/p>\n\n\n\n When you switch vendors, candidate data must be handled carefully under DPDPA:<\/p>\n\n\n\n Data collected by Vendor A cannot transfer to Vendor B without fresh candidate consent.<\/strong> This means active cases mid-check may require re-consent if the new vendor needs the original documents.<\/p>\n\n\n\n Vendor A must delete candidate data per your retention policy after transition.<\/strong> Get written confirmation of deletion. DPDPA Section 8(7) requires Data Processors to delete data when the purpose is fulfilled.<\/p>\n\n\n\n Document the transition.<\/strong> The Data Protection Board may someday ask: how did you ensure data security during the vendor transition? Your answer should be a documented migration protocol, not a shrug.<\/p>\n\n\n\n SpringVerify’s onboarding team assigns a dedicated migration specialist for switching companies \u2014 handling parallel testing setup, HRMS integration, consent workflow migration, and data transition documentation. The 6-week timeline is standard for their migration process.<\/p>\n\n\n\n Key Takeaways:<\/strong><\/p>\n\n\n\n \u2022Vendor switching takes 6-8 weeks with proper planning \u2014 the “nightmare” reputation is vendor FUD<\/p>\n\n\n\n \u2022Parallel testing with 25-30 real checks is the single most important step \u2014 it replaces opinion with data<\/p>\n\n\n\n \u2022DPDPA requires specific data handling during transitions: no bulk data transfer, deletion confirmation from old vendor<\/p>\n\n\n\n \u2022Review your current contract for notice periods, auto-renewal, and minimum volume penalties before notifying<\/p>\n\n\n\n \u2022The 30-day post-cutover review is where you prove the switch was worth it \u2014 measure everything<\/p>\n","protected":false},"excerpt":{"rendered":" The VP HR at a 600-person IT services company in Pune had been unhappy with their BGV vendor for 18 months. Amber rates above 12%. TAT averaging 14 days for employment checks. An “account manager” who responded to emails approximately never. But every time she raised switching, the same objection came back from her team:<\/p>\n","protected":false},"author":1026,"featured_media":512404,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[102665,102674],"tags":[14,130,131],"class_list":["post-512403","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-background-check","category-sv-in-customers","tag-background-checks","tag-springverify","tag-springverify-india","disable-dropcap","disable-2-columns"],"yoast_head":"\nPhase 2: New Vendor Setup (Weeks 2-4)<\/h3>\n\n\n\n
Phase 3: Parallel Testing (Weeks 4-6)<\/h3>\n\n\n\n
Phase 4: Cutover (Weeks 6-8)<\/h3>\n\n\n\n
The DPDPA Migration Complication<\/h2>\n\n\n\n