ABOUT THE COMPANY :

ProVal Technologies is a master managed services provider (MSP). Our forte is managed services, and we partner with some of the most successful and innovative IT Service providers to provide them with 24x7 network operations center (NOC) support, and remote infrastructure management across leading technology platforms.

JOB SUMMARY :

Owns customer-facing discovery, migration solution design, effort estimation, and technical risk planning for M365/Azure/multi-cloud migration projects. Leads presentation of solutions to customers. Provides technical oversight to delivery team. Not a hands-on execution role but may require hands-on involvement if the execution team needs help. Total experience 12-15 years.

CORE RESPONSIBILITIES :

- Lead discovery calls to identify migration-specific risk : legacy customizations, integrations, permission structures, data volume, prior migration history.

- Assess source environments (on-prem AD, legacy file servers, other tenants, non-Microsoft platforms) for migration risk.

- Design migration sequencing : batch/wave planning, pilot groups, cutover windows, coexistence periods, rollback strategy.

- Produce effort-estimates accounting for migration-specific unknowns (data cleanup, permission remediation, throttling limits, dependency risk).

- Present migration plans and risk/contingency plans to customers, including US/international stakeholders.

- Identify and plan around common failure points : mailbox throttling/delta sync failures, SharePoint/OneDrive/Teams permission and metadata loss, DNS/MX cutover timing and mail flow disruption, Entra ID/Intune device re-enrollment failures, licensing/quota exhaustion mid-migration, dependency surprises from customizations or integrations.

- Define validation/testing checkpoints and rollback contingencies per project, prior to execution.

- Act as escalation point for delivery team on high-risk or unfamiliar technical scenarios.

- Convert recurring risk patterns into reusable playbooks/checklists.

- Mentor migration engineers on risk recognition, not just tool execution.

REQUIRED SKILLS :

- 5+ years in migration/transformation delivery, MSP or consulting environment.

- End-to-end ownership of multiple migration projects across at least two of : SharePoint/OneDrive/Teams, Exchange/mailbox, Entra ID/Intune/device, Azure infrastructure.

- Practical exposure to at least one tool in each category :

1. Content/collaboration migration (ShareGate, Quest, or equivalent)

2. Mailbox/tenant migration (BitTitan MigrationWiz, or equivalent)

3. Identity/device migration (ImmyBot, Cloudiway, ProfWiz/Forensit User Profile Wizard, or equivalent)

- Working knowledge of on-prem legacy environments (Active Directory, Windows File Server, virtualization platforms) as migration source context.

- Effort estimation and scoping experience specific to migration risk, not target-state design.

- Demonstrated experience leading migration-scoping conversations with US/international customers.

- Working knowledge of batch/wave planning, pilot testing, coexistence strategy, rollback planning.

SCREENING NOTES :

- In interviews, require the candidate to describe specific past migration failures/near-misses and how they were resolved. Generic tool-usage answers without concrete failure examples indicate insufficient depth.

- For each required tool category, confirm the candidate can explain what the tool does and does not handle well - not just name it. Tool-naming without functional understanding indicates surface-level exposure.

- Avoid candidates whose migration exposure is limited to 1-2 projects within a larger generalist infrastructure/architect role.

- Avoid candidates positioning themselves primarily as environment designers or governance/licensing specialists.

BENEFICIAL SKILL SET :

- Exposure to a broader range of tools beyond the required minimum per category.

- Exposure to non-Azure destinations (AWS, GCP) for migration scoping.

- AZ-104, AZ-305, or MS-102 (preferred, not mandatory).

- Prior experience mentoring/building a technical team.

- Confident client-facing presence under pressure (escalations, tight cutover windows).

- Risk-oriented thinking by default.

- Able to translate technical risk into business-level language.

- Willing to mentor, not just direct.