Access by approved implementation.

Resource

Legacy Portal Migration

A migration approach for programs moving away from spreadsheets, email loops, and legacy upload-and-chase workflows.

Access is provisioned through approved institutional implementation.

AnchorGrey Workspace

Director workspace

Spring 2026 cohort

Tenant provisioned
42Learners
24Complete
8Action needed
Reviewer workflow5
Program review11
Expiration watch7

Learner checklist

TB documentation
MMR record
Program form

Reviewer queue

Correction needed
Escalation

Migration starts with the workflow, not the vendor switch.

Programs can move away from fragmented portals, spreadsheets, and inbox loops by first mapping requirements, review responsibility, reporting defaults, and tenant provisioning needs.

  • Map the current requirement set before changing systems.
  • Define visibility defaults and reviewer responsibilities.
  • Start with a narrow cohort or workflow before expanding.
  • Use controlled tenant provisioning for institutional rollout.
Plan the migration path