Migrating Apple Devices to FileWave from Another MDM using ASM/ABM

What

Apple School Manager (ASM) and Apple Business Manager (ABM) now include a device assignment feature that allows you to move DEP/ADE devices from one MDM server to another without requiring physical device access or a factory reset. FileWave can serve as the receiving MDM server in this migration process, making it possible to transition devices from competing MDM solutions with minimal disruption. Note that this functionality of a forced move is new in the '26 versions of the Apple OS versions. 

When/Why

Use this feature when you're switching to FileWave as your primary MDM and want to migrate existing DEP/ADE enrolled devices without losing enrollment or forcing users through complex re-enrollment processes. This is especially valuable when:

• You have an established fleet on another MDM and want to consolidate to FileWave
• You want to avoid factory resets or complex manual re-enrollment workflows
• You need to preserve device configurations and user experience during the transition
• You're testing FileWave's MDM capabilities before committing to a full migration

How

Prerequisites

1. FileWave instance registered as an MDM server in your ASM/ABM account (follow standard MDM setup)
2. Your existing MDM server still registered in ASM/ABM
3. At least one test device to validate the process

Step-by-Step Process

1. Assign Device Management in ASM/ABM

1. Log in to Apple School Manager or Apple Business Manager
2. Navigate to your device list and select a test device (start with 1–2 devices, not your entire fleet)
3. Click the ... (three-dot) menu in the top right corner
4. Select Assign Device Management
5. Choose FileWave as the destination MDM server
6. Click + Add Deadline to set when the migration occurs
   • Choose the soonest available time if you want the device to move immediately
7. Confirm the assignment

2. Synchronize with FileWave

1. On your FileWave server, navigate to Assistants → ADE Association Management
2. Click Synchronize to pull the latest device list from Apple
3. The moved device should appear in the ADE device list within a few moments

If the device doesn't appear:

• Hold Option (⌥) while clicking the Synchronize button
• The button text will change to "Full Sync"
• Click it to perform a complete sync; the device should now appear

3. Assign Enrollment Profile

1. Locate the newly migrated device in your FileWave ADE device list
2. Verify an enrollment profile is assigned to it
3. If no profile is assigned, select an appropriate enrollment profile and assign it
4. Click Sync with Apple to confirm the assignment

4. User Migration Prompt

Once Apple detects the enrollment profile is assigned:

• The device will automatically receive a prompt to migrate MDM servers
• For the user: the process is straightforward—they simply accept the on-device prompts
• Users do not need to understand or interact with MDM details; the migration is transparent to them

Platform

Note: This process applies to all Apple platforms enrolled via DEP/ADE.

Related Content

• FileWave MDM Server Setup in Apple Business Manager
• ADE Association Management Best Practices
• VPP App Assignment in FileWave
• Device Enrollment Profiles in FileWave

Digging Deeper

VPP Apps and Migration

One critical consideration during migration is app continuity. If your devices were using VPP (Volume Purchase Program) apps assigned via the previous MDM:

• Apps won't automatically transfer to FileWave
• After migration, you must configure VPP app assignments in FileWave to ensure users retain app access
• Apps may be removed from devices if they're no longer available through the new MDM during the transition
• Test this scenario on your pilot devices to understand timing and user impact

Recommendation: Audit which VPP apps are currently assigned on your test devices, then set up the same apps in FileWave before migration to minimize disruption.

Testing Strategy

Migrating devices in small batches is essential:

1. Test batch (1–2 devices): Verify the assignment, sync, and enrollment profile assignment works as expected
2. Observe user experience: Confirm users receive prompts and can migrate without assistance
3. Check app availability: Ensure critical apps (especially VPP) are available on FileWave post-migration
4. Check configurations: Verify that any device configurations or restrictions are re-applied properly
5. Rollout in waves: Once validated, migrate in small groups (10–50 devices) rather than all at once

This phased approach prevents fleet-wide issues and gives you time to address any unexpected problems.

Timing and Deadlines

• If you don't add a deadline in ASM/ABM, the device assignment will remain pending
• The deadline determines when Apple will initiate the migration prompt on the device
• Devices don't migrate instantaneously; allow time for Apple's systems to process and push the prompt
• Monitor ADE Association Management sync logs to see when devices are enrolled with FileWave

If Migration Stalls

If a device doesn't complete migration:

1. Verify the enrollment profile is still assigned in FileWave
2. Check that the device has network connectivity
3. Perform another Full Sync (Option + Synchronize) in ADE Association Management
4. Check device logs on the client to see if there's a prompt pending user action