Legacy MDM to AirWatch: A Migration Checklist for Australian Teams

Australian organisations are increasingly reviewing the mobile device management tools they deployed a decade or more ago, and many are discovering that the platforms cannot keep pace with modern workforces. In Sydney corporate towers, Melbourne contact centres, and Pilbara mining camps, the same pattern is emerging: a legacy MDM solution that was once considered state-of-the-art now struggles with cloud-first applications, hybrid identity, and the bring-your-own-device expectations of staff who rotate between the office, the home, and remote sites. Migrating from legacy MDM to AirWatch gives IT teams a single console to manage smartphones, tablets, laptops, and ruggedised devices across every location.

The move is rarely just a software swap. It involves reconciling device inventories, reworking compliance policies to align with the Notifiable Data Breaches scheme and the Privacy Act 1988, retraining administrators, and reassuring end users that their personal data will remain private. With a structured checklist, the transition can be completed without disrupting field engineers at a Brisbane water utility, clinicians at a regional Victorian hospital, or sales teams travelling between Perth and Adelaide.

Why Australian Companies Are Replacing Legacy MDM Solutions

The shift away from older mobile management platforms is driven by three forces that are particularly visible in Australia. First, the rapid adoption of hybrid work has stretched legacy tools beyond their original design, especially for organisations with workers spread across the Murray–Darling basin or travelling between Hobart and Darwin. Second, the local regulatory environment has tightened, with the Australian Cyber Security Centre regularly publishing guidance that legacy MDM configurations simply cannot enforce. Third, the cost of running parallel systems, one for compliance reporting and another for modern app delivery, has become difficult to justify in boardrooms focused on cloud consolidation.

AirWatch addresses these pressures through a unified endpoint management approach. Administrators can enrol iOS, Android, Windows, macOS, and ChromeOS devices from the same console, apply conditional access policies, and integrate with identity providers such as Okta or Microsoft Entra ID. For Australian teams, this also means less time spent juggling vendor licences and more time focused on the specific needs of sectors like resources, healthcare, retail, and professional services.

Planning the Migration: Scope, Timelines, and Stakeholders

A migration succeeds or fails in the planning phase, so the first task is to define scope with precision. Begin by listing every business unit that depends on mobile devices, from the executive floor of a Melbourne CBD headquarters to the depot drivers servicing regional New South Wales. Capture the device types in use, the applications installed, the data classification tiers, and the existing compliance posture. This inventory becomes the single source of truth that the migration plan is built around.

Next, identify the stakeholders who must sign off on the project. In larger Australian enterprises, this typically includes the CIO, the head of information security, the legal and privacy officer, the facilities manager responsible for remote offices, and representatives from HR and end-user-facing branches such as sales. Establish a steering committee that meets fortnightly and a working group that handles the technical detail. Build a timeline that accounts for end-of-financial-year reporting deadlines, public holidays such as the King's Birthday long weekend, and any planned technology refreshes already scheduled by procurement.

Device Discovery and Inventory in the Existing Environment

Before any data is moved, the existing estate must be mapped thoroughly. Run discovery tools across the legacy MDM to identify every enrolled device, the operating system version, the last check-in timestamp, and the assigned configuration profile. Where the legacy platform lacks modern reporting, supplement it with agent-based scans of corporate networks and surveys of line-of-business application owners. The goal is to expose shadow devices that may not be officially enrolled but still hold corporate data.

In a typical Australian rollout, this stage often uncovers surprises: rugged tablets used in Pilbara mining operations that were enrolled years ago and never updated, or personal iPhones accessing email in a Sydney law firm that sit outside the formal compliance boundary. Document each finding and decide whether to migrate, retire, or reclaim the device. Tag every asset with a clear status so the AirWatch administrator group inherits an accurate baseline on day one.

Preparing AirWatch for a Smooth Cutover

Configuration of the new environment should begin well before users are moved. Stand up the AirWatch tenant in the closest supported region, apply the recommended security baseline, and integrate it with the corporate directory. Define organisational groups that mirror the Australian operating model, such as state-based divisions, business units, and a dedicated group for field workers in remote locations. Within each group, configure profiles, compliance policies, and application delivery rules.

Equally important is the catalogue of applications. Audit the existing enterprise app store, remove anything redundant, and prepare a clean set of public and internal apps for AirWatch deployment. For organisations that distribute in-house apps to clinicians at a Victorian hospital or engineers at a Queensland rail project, prepare the binaries, code signing certificates, and deployment rules in advance. Test push notifications, app configuration payloads, and single sign-on flows so that the user experience matches what the help desk has promised.

Data Migration, Policies, and Compliance Alignment

Migrating data and policy content requires care, particularly when regulated information is involved. Export device records, configuration profiles, compliance policies, and certificate inventories from the legacy MDM in a documented format, then map each item to its AirWatch equivalent. Where the platforms use different terminology, create a translation table so administrators and auditors can follow the chain of custody. Retain migration logs for at least seven years to satisfy the record-keeping obligations commonly referenced by the Office of the Australian Information Commissioner.

Policy alignment is the most sensitive part of the exercise. Review the legacy rule set against current Australian Privacy Principles, the Notifiable Data Breaches scheme, and any sector-specific obligations such as the My Health Records Act for healthcare providers or APRA CPS 234 for financial services. Adjust AirWatch policies so that encryption, remote wipe, jailbreak detection, and data loss prevention controls match or exceed the previous baseline. Pay particular attention to personal data residency, especially for organisations that operate data centres in both Australia and offshore jurisdictions.

Pilot Testing and Phased Rollout Across Sites

A pilot run is the safest bridge between preparation and full deployment. Select a representative group of users, ideally spread across multiple sites such as the Sydney head office, a regional Queensland branch, and a small team in Perth. Enrol their devices through AirWatch using the staged workflows, validate that mail, calendar, internal applications, and VPN access continue to function, and gather feedback through a short survey. Use this window to refine help desk scripts and run books before they are needed at scale.

Once the pilot stabilises, move into a phased rollout. Begin with a single business unit or region, monitor enrolment success rates, device compliance scores, and help desk load for at least a week, then expand to the next cohort. In organisations with thousands of devices spread across Australian time zones, this measured approach prevents the support desk from being overwhelmed and gives administrators time to resolve issues before they affect a larger population.

Post-Migration Support, Training, and Continuous Optimisation

The work does not end when the last device is enrolled. Schedule a hyper-care window of two to four weeks during which the migration team provides extended support, monitors dashboards, and addresses edge cases. Deliver targeted training to administrators, help desk staff, and end users, with sessions tailored to roles such as field technicians in remote Western Australia or executive assistants in a Sydney corporate suite.

After hyper-care, transition to a continuous optimisation cycle. Review AirWatch dashboards monthly, retire policies that are no longer relevant, and update the catalogue as new applications are released. Run annual disaster recovery exercises that simulate the loss of the console, and rehearse the breach response process with the security team. With disciplined follow-through, the migration delivers not just a new platform but a stronger mobile security posture across the entire Australian operation.

Recommendations for a Controlled Migration

Migrate to AirWatch now and run a 30-day free trial to validate the platform against your specific device estate, then request a tailored quote through the AirWatch sales team. Start the trial at airwatch.com to put the migration checklist into action across your Australian sites.