Do we need to change every part of our workplace technology?
No. The brief can focus on a collaboration space, a device group or a defined part of the working environment. Identify the dependencies so that a smaller change does not leave an important access, application or support decision unresolved.
Will existing access permissions be carried across unchanged?
Do not assume that copying the current arrangement is the right outcome. Agree the intended access with the information owner, then check it during the project. Any migration should include the access checks appropriate to its scope and the systems involved.
Can we retain our current devices and applications?
Discuss what you want to retain during scoping. Compatibility, support status, licences and the requirements of affected users need to be checked. The agreed design should make any replacement or application change clear before rollout.
Are software licences and new devices included?
Only if the proposal includes them. Separate the implementation work from equipment, subscriptions and any migration tools so the full cost and ongoing commitments are visible.
Does the project include staff training?
Training can be scoped around the affected roles and tasks. Confirm the audience, format, materials and any administrator handover in the proposal. A technical deployment alone does not define the level of user support included.
Who manages the environment after rollout?
Agree that before delivery. Content owners, administrators and the support team may have different responsibilities. Record who approves access changes, maintains the configuration and handles requests, with any ongoing managed service specified separately.
What should we arrange before a Microsoft 365 migration starts?
Work out who holds administrator access to the current email system, and confirm licensing early, because both affect which approach is available. You will also need to nominate owners and make authorised access available. Microsoft documents several routes for moving Exchange mailboxes, including cutover, staged, hybrid and IMAP, chosen by source system and size. IMAP, for example, does not carry contacts, calendars or tasks, and mailboxes must exist before it runs. The method is agreed before cutover.
How do we decide which files move to SharePoint and which stay behind?
Start with decisions rather than tools. Define sites, libraries, owners and access, then map source folders to destinations and test representative files and permissions before agreeing cutover. Microsoft’s SharePoint Migration Tool lists file shares as a supported source, but choosing a tool does not settle what should move, who owns it or who can see it. Anything left behind, and how people will find it afterwards, should be agreed up front.
What should we confirm before moving to Teams Phone?
Teams Phone arrangements vary, and not every deployment uses Access4. Microsoft describes different ways to connect Teams to the phone network, including Calling Plans, Operator Connect and Direct Routing, and each divides responsibility between you and the provider differently. Users also need the right Teams Phone licence. For selected Access4 services, the provider may lead platform and call-flow work while Subnet handles the agreed local deployment and transition tasks. Handsets, decommissioning and training are included only when specified.
Can we keep our existing phone numbers?
Usually, when changing providers, but it depends on the number and the providers involved. Number porting follows the relevant providers’ processes. The Australian Communications and Media Authority explains that you request the port through the new provider, who runs identity checks, that the new provider is not obliged to accept a ported number, and that disconnected numbers cannot be ported. Mobile ports are typically quick while landlines can take longer, so plan the changeover around the slowest number.