Virtual assistant file migration controls

Key takeaways

• Use a written brief and definition of done.
• Keep approvals and escalation rules visible.
• Review quality before expanding the workflow.

# Virtual assistant file migration controls

Map source folders, record classes, owners, naming, retention, permissions, and destination. Pilot a representative slice and compare counts, versions, links, and access before expansion.

Applying virtual assistant file migration controls

Migration risk is concentrated in exceptions: duplicate names, old versions, broken links, restricted folders, and records with no clear owner. Pilot one representative slice, compare source and destination counts, and stop when the reconciliation explains every difference rather than assuming the transfer is complete.

Role boundary and review

The assistant can map files, flag collisions, and maintain an exception register. The owner approves retention, permission, and deletion decisions. Keep the source snapshot, destination check, unresolved items, and rollback or recovery point together before the next migration slice begins. the [services library](/services) helps distinguish file administration from retention decisions, while the [[provider vetting guide](/provider-vetting)](/provider-vetting) frames access and continuity. [NIST guidance](https://www.nist.gov/itl/smallbusinesscyber) is a useful safeguard reference. ### Migration evidence Keep source and destination counts, version and permission exceptions, owner decisions, recovery point, and pilot scope.