Enterprise Domain Migration

Acrisure grows through acquisition. Each newly acquired company brings its own identity, endpoints, and productivity stack that must land inside Acrisure's Microsoft environment quickly and consistently. Hypercare covers that transition window, where users still need to work while their devices, accounts, and access are cut over.

Migrations had to be executed the same way by every technician, on tight windows, without disrupting the acquired company's day-to-day work. Small variations in device rename, identity join, group membership, or app configuration would surface later as access issues, MFA prompts, or broken collaboration. The workflow needed to be both fast and reproducible, and new peers needed a way to learn it without shadowing every step.

Migration technician executing the workflow on production users and devices, and an informal peer resource who refined the steps, wrote reusable templates, and walked other technicians through the process when managers referred them over.

• Ran end-to-end migrations for acquired-company users and devices during hypercare windows.
• Refined the workflow into a repeatable sequence that peers could follow without guesswork.
• Produced reusable templates and checklists covering identity, endpoint, and app configuration.
• Delivered live walkthroughs for peers referred by managers who wanted to see the workflow end to end.
• Validated each migration with the user before handoff to reduce follow-up tickets.

1. 01

   Confirm user identity and readiness

   Verify the user, confirm the migration window, and set expectations for downtime.

2. 02

   Establish remote access

   Bring the device into a supportable remote session for the technician.

3. 03

   Validate OneDrive backup and browser-data readiness

   Confirm files and browser data are captured before any destructive step.

4. 04

   Rename the device where required

   Align the device name with Acrisure's naming standard.

5. 05

   Join the device to Microsoft Entra ID

   Move the endpoint into Acrisure's identity plane.

6. 06

   Assign the primary user and required access groups

   Set the primary user and add the correct user and device groups.

7. 07

   Configure Windows Hello for Business

   Enable passwordless sign-in per Acrisure's standard.

8. 08

   Enroll through Microsoft Intune and Company Portal

   Bring the device under Intune management and deliver required apps.

9. 09

   Configure Microsoft 365 applications and collaboration tools

   Outlook, Teams, OneDrive, and the standard collaboration stack.

10. 10

    Restore user data and preferences

    Reattach OneDrive content and browser data so the user resumes work quickly.

11. 11

    Validate security tools, printing, and connectivity

    Confirm endpoint security, VPN, printing, and network access all work.

12. 12

    Complete final checks and user handoff

    Walk the user through sign-in, MFA, and the tools they use daily before closing the migration.

Steps are described at a high level. Internal naming conventions, group names, and account details are intentionally omitted.

Migrations landed with less rework and fewer follow-up tickets, peers ramped faster because they had a documented sequence to follow, and managers had a technician they could point new team members to when they needed to see the workflow executed correctly.

• Ability to standardize a complex, multi-system workflow under time pressure.
• Comfort operating across identity, endpoint, and productivity tooling in a single engagement.
• Instinct to document and templatize instead of keeping tribal knowledge.
• Peer leadership recognized informally by management through walkthrough referrals.