Phase 1: Analysis
During this phase, we provide a survey to the client and analyze the existing technical infrastructure within their Microsoft tenant.
What do we need from IT?
- An IT contact with the M365 tenant Global Admin role. That person will receive a request from Microsoft and will check the box providing our application with access to the client’s Microsoft tenant. This does not require a meeting or call.
- Possible access to all other legacy file repositories. Typically, we will request access to file servers but can include Google properties, desktop file dumps, NAS, etc. This usually requires a 15-minute meeting.
Phase 2: Workshop
We meet with key members of the client’s team to architect their new SharePoint and Teams environment. We map all existing file locations during this phase.
What do we need from IT?
- Access to the client’s Microsoft Tenant via an actual login. A Global Admin is ideal, but Teams and SharePoint Admin is sufficient.
- Access to all other legacy file repositories, if not already provided in Phase 1. Includes file servers, Google properties, desktop file dumps, NAS, etc.
- Quick 15-minute scrum to discuss the details of the technical environment.
Phase 3A: Architecture
We define the client’s entire team structure, including Teams, Channels, SharePoint file folders, and policy frameworks. Policy outcomes depend on client input.
What do we need from IT?
- Assist in managing the file server environment in preparation for migration (e.g., installing SharePoint Migration Tools).
- Policy input:
- Local Storage: Are files on personal devices backed up? Whatis your stance on local storage?
- External Sharing: How should SharePoint file links beshared? Publicly, with anyone, or restricted?
- File Retention: Do you have a retention policy? If not, whatpolicy should be adopted?
- User Access Requests: How should requests for new groups orusers be handled in Entra ID?
Phase 3B: Migration
If AP Logic is performing the migration, we will move the bulk of files beforehand and conduct differential migration on the agreed migration date(s).
Afterward, legacy systems are locked down to avoid rollback.
What do we need from IT?
- A technical contact with 24/7 cellphone access; AP Logic will also be available 24/7.
- Calendar commitments for migration dates. We will reach out after client confirmation.
- IT confirms file repository or tenant backups, including the resource name and last backup date. Alternatively, confirm no backup is provided and the client is aware.
- IT confirms and executes and new policies to lock down access to legacy file repositories, ensuring users no longer write to those locations.
Phase 4: Support
If the client signs an agreement for ongoing services with AP Logic, we provide continued support post-migration.
What do we need from IT?
- Confirm the method for customer escalation from IT to AP Logic for Teams and SharePoint-related requests.
- Clarify types of requests escalated to AP Logic.
