Migration center
A controlled move,not a copy-paste weekend.
Bring your current credential list in through a documented template, map it to clients and groups, rotate what was exposed during export and retire the old system on a checklist.
Cutover
Three phases with no gap in access.
Step 1
Import
Load clients, systems and credentials from a CSV using the documented PulseHireX template, or from a browser or password-manager export.
Step 2
Assign
Map imported systems to clients and groups so access matches how the team actually works.
Step 3
Rotate & retire
Rotate credentials after cutover, confirm launches work, then run the legacy subscription shutdown checklist.
Care points
Where migrations usually go wrong.
Exported files
Many migration exports—especially CSV exports—contain credentials in plaintext or another readily readable form. Treat every migration file as highly sensitive unless the exporting product explicitly protects it.
Stale entries
Import is the moment to drop systems nobody has used in a year.
Over-broad access
Rebuild access from groups instead of replicating everyone-sees-everything.
Untested resources
Flag anything not successfully launched after import.
Duplicate logins
Merge duplicates so rotation only has to happen once per system.
Legacy shutdown
Close the old subscription only after launches are verified in PulseHireX.
Secure migration controls
Built-in safeguards for sensitive cutover data.
Secure upload channel
Import files are uploaded over TLS through an authenticated admin session, not emailed or shared in chat.
Temporary staging
Imported rows are staged in a short-lived workspace where they can be reviewed before being committed to live resources.
Automatic deletion after import
The original upload and any intermediate staging rows are removed once the migration is confirmed complete.
No email attachments
Exports and credential lists are never accepted or distributed by email; all transfer happens inside the admin console.
Import hash/manifest
Each upload is logged with a manifest so you can verify which rows were imported, by whom, and when.
Migration audit event
Every import, assignment, rotation and cleanup step is recorded in the audit trail for compliance reviews.
Secure cleanup confirmation
Admins confirm deletion of staging data and source files before the migration is marked finished.
Bring your current list and we will map it.
Send the export structure and we will confirm the template and cutover order.