Job Title: Business Systems Analyst/Application Migration Coordinator
Location: Remote
We are running an enterprise-wide application modernization program involving Azure & Colo migration and legacy data center exit. Every application in scope needs one person to own the process side of the move, and that is the BSA. Despite the title, this is a coordination job rather than a traditional business analyst job. The BSA is the main contact for an application team, runs the calls, coordinates with Architecture, Cyber, Systems, Network and Testing, and keeps the application moving through each migration gate with the right documentation behind it. Most BSAs cover several applications at once.
Responsibilities
- Single point of contact for assigned application teams and liaison to the delivery teams
- Schedule and run the recurring calls (discovery, working sessions, checkpoints, governance prep)
- Track status, dependencies and progress against the migration schedule in ServiceNow, and keep the records accurate for program reporting
- Log issues, follow them through to closure, and explain them clearly to both the app team and program leadership
- Know what each gate requires, collect the approvals and artifacts ahead of time, and confirm everything is in place before the application is presented
- Coordinate handoffs between design, build, test and governance
- Escalate blockers early with enough detail for a manager to act on, and send weekly status
- Support cutover and go/no-go
- Identify, run and document process and program improvements that speed up and mature the enterprise modernization and migration program
Applications move through Design, Dev, Cert, Pre-Prod and Prod/Go-Live. Testing, approvals and documentation are required at every gate.
What we need
- 3+ years as a BSA, project coordinator, technical PM or similar
- Experience on data center, infrastructure or cloud migration work
- Strong communication, which is the most important part of this job. Can run a call with a dozen people from different teams, keep it on track, and write a short clear update afterward
- Proactive follow-up. Chases open items instead of waiting for them to come back
- Enough technical fluency to follow the discussion and describe an issue accurately, covering things like app dependencies, environments, IP and DNS changes, firewall rules, certificates, backup and DR, cutover and rollback
- Familiar with change management and governance (change records, CAB, approval evidence)
- ServiceNow or a comparable ITSM tool
- Organized, and effective across teams without direct authority
Nice to have:: prior data center exit or wave-based migration program, Azure or AWS exposure.