The 14-Day Switch Plan: How to Move From Deel IT, Workwize, or Hofy to Rayda Without Downtime

Switching to Rayda from Deel IT, Workwize, or Hofy takes 14 business days with zero downtime when you follow this plan. The process covers inventory audit (days 1–3), parallel operations setup (days 4–6), MDM and HRIS integration transfer (days 7–10), and full cutover with validation (days 11–14). Rayda's migration team manages the heavy lifting. Here is the complete day-by-day playbook.

If you are already certain your current vendor is not working, talk to Rayda's team and they will build your custom transition plan. If you want to understand the full process first, keep reading.

This guide covers every milestone, owner, and completion criterion across all 14 days, plus vendor-specific notes for migrating from Deel IT, Workwize, or Hofy.

What Does a 14-Day Device Management Migration to Rayda Look Like?

Switching to Rayda follows four phases across 14 business days: inventory audit, parallel operations, MDM and HRIS integration transfer, and full cutover. Each phase has defined owners, daily milestones, and clear completion criteria so nothing stalls mid-migration. Rayda's migration team runs alongside your IT lead throughout.

Most IT teams assume switching device management vendors means weeks of chaos, frozen orders, and angry new hires waiting for laptops. In practice, the chaos comes from not having a plan. A structured device management migration plan removes the ambiguity. You know what happens on day 3, who owns it, and what "done" looks like.

Here is the full 14-day Gantt-style breakdown.

The plan assumes your current vendor has standard data export functionality, which Deel IT, Workwize, and Hofy all support. If your inventory data is in spreadsheets rather than a vendor portal, add one buffer day for cleaning. (If spreadsheet-based tracking is still your reality, this post on moving away from spreadsheet-based device tracking is worth reading first.)

What Should You Complete in Days 1–3 (Inventory Audit and Kickoff)?

Days 1–3 of the switch to Rayda focus on understanding exactly what you have. You export your full asset inventory, identify devices by status (active, in transit, in storage, pending retrieval), and share the data with Rayda's migration team for a gap analysis. By end of day 3, you have a prioritised list of what moves first.

Day 1: Kickoff Call

Your Rayda customer success manager (CSM) runs a 60-minute kickoff. You agree on the migration lead from your side, set communication cadence, and document any constraints: upcoming new hire start dates, devices in transit, contract end dates with your current vendor.

One thing to flag early: the industry average contract lock-in for device management vendors is 12 months. Know your notice period before day 1. If you are mid-contract, Rayda can run in parallel during the overlap so you are not paying for nothing.

Day 2: Asset Export

Pull a full CSV export from your current vendor's portal. Every device, every status. Deel IT, Workwize, and Hofy all support this. The export should include: device serial number, assigned user, current location, MDM enrollment status, and device condition.

Day 3: Gap Analysis

Rayda's migration team reviews your export and flags three things: devices with missing or incorrect data, locations where Rayda's local sourcing differs from your current vendor (usually an upgrade, since Rayda covers 170+ countries with local stock in APAC, LATAM, and Africa), and any open orders that need redirecting.

By end of day 3, you have a written gap report. Nothing moves forward without it.

How Do You Set Up Parallel Operations in Days 4–6?

Parallel operations mean both your old vendor and Rayda are active at the same time, for a defined window. This is the safest part of any device management migration plan. No new hires are blocked, no devices go dark, and you have a fallback if anything unexpected surfaces. Days 4–6 cover portal setup, MDM staging, and HRIS read access.

Day 4: Rayda Portal Setup and Test Order

Your Rayda portal is provisioned and configured with your company details, device preferences, and approval workflows. A test order is placed to validate delivery speed in your primary deployment regions. Rayda's delivery window is 8–12 days in most markets, including emerging markets where competitors often run 30–60 days. (If slow international delivery has been a pain point, here is why laptop delivery delays happen and how to fix them.)

Day 5: MDM Profile Migration

This is where most IT teams get nervous, but it is simpler than it sounds. Apple's device-management migration feature, supported on iOS 16 and later, allows managed devices to migrate MDM enrollment without a full wipe. Your IT lead clones existing configuration profiles into Rayda's MDM environment and validates them in a staging setup before touching any live device.

For Windows devices, the process follows Microsoft's recommended Intune migration path, which Rayda's team has documented for common configurations.

Day 6: HRIS Read Access

Grant Rayda read-only access to your HRIS (Workday, BambooHR, HiBob, or whichever you use). Rayda runs a test sync to confirm new hire data flows correctly. Auto-provisioning will go live on day 9, but the connection needs to be confirmed now.

How Do MDM and HRIS Integrations Transfer in Days 7–10?

MDM and HRIS integrations transfer in two stages: first a controlled cohort migration (days 7–8), then full integration testing and open order redirection (days 9–10). By end of day 10, Rayda is handling all new provisioning, and your old vendor is in wind-down mode. No device goes unenrolled during the transition.

This is the phase where the migrate to Rayda playbook diverges most from ad-hoc vendor switches. Without a defined cohort sequence, teams accidentally unenroll devices before Rayda's profiles are ready, leaving devices in an unmanaged state. That is the only real risk in this process, and the cohort approach eliminates it.

Day 7: First Cohort MDM Migration

Pick 5–10 devices as your first cohort. These should be active devices assigned to users who are not onboarding that week, so there is no pressure if anything needs a second pass. Migrate them to Rayda's MDM enrollment and confirm each device checks in correctly.

Security note: before any MDM migration, confirm your data handling policies are documented. NIST guidance on mobile device security recommends validating enrollment status before and after any MDM transfer to avoid gaps in policy enforcement.

Day 8: Full Parallel Operations

Both vendors are live. Your old vendor still covers any devices not yet migrated. Rayda handles all new orders. This overlap is intentional. If a device in your old vendor's system needs retrieval or replacement during this window, that vendor handles it. Nothing falls through.

Day 9: HRIS Auto-Provisioning Live

The HRIS integration goes fully live. A test new hire record is created and the system confirms a device order triggers automatically. From this point, any new hire added to your HRIS will automatically trigger a Rayda provisioning workflow. This is particularly useful if you are hiring in multiple regions. For teams expanding into Southeast Asia or Latin America, the local sourcing difference is significant. Rayda stocks devices locally rather than cross-shipping, which cuts delivery time from 30–60 days to 8–12 days in most emerging markets.

Day 10: Open Order Review

Any outstanding orders placed with your old vendor are reviewed. Orders already in production or in transit stay with the old vendor to completion. Orders not yet fulfilled are cancelled and re-placed through Rayda. Your migration lead documents every redirect decision so there is a clear audit trail.

What Happens During Full Cutover and Validation in Days 11–14?

Full cutover means your old vendor's access is suspended and Rayda becomes the single system of record for all device management. Days 11–14 cover access revocation, a full device validation sweep, the first live Rayda-only deployment, and migration sign-off. By end of day 14, the switch to Rayda is complete.

Day 11: Cutover

Your IT lead revokes admin access to the old vendor portal and confirms Rayda is the primary. Any remaining devices still enrolled in the old MDM are migrated in a second cohort. This is usually a small tail, mostly devices that were in transit or being prepared for retrieval during the earlier phases.

Day 12: Validation Sweep

Every active device is accounted for in Rayda's portal. Serial numbers, assigned users, locations, and MDM enrollment status are confirmed. Target: 100% of devices reconciled. Any discrepancy is flagged and resolved before day 13.

This is also a good time to review any devices flagged as idle or unaccounted for. If device retrieval has been inconsistent under your previous vendor, this guide on retrieving company laptops from remote employees covers how to tighten that process going forward.

Day 13: First Live Deployment

The first new hire device order is placed and fulfilled entirely through Rayda. This is a deliberate milestone. It confirms the full procurement-to-deployment workflow is live, not just the portal access.

Day 14: Sign-Off and Week 3 Plan

Your migration lead and Rayda CSM sign off on the migration. Rayda delivers a post-migration plan covering device refresh scheduling, retrieval workflows, and any open questions from the audit. You are done.

What Are the Key Differences When Migrating From Deel IT vs. Workwize vs. Hofy?

The migrate to Rayda playbook is the same for all three vendors, but each platform has specific considerations that affect how fast certain phases move. The table below covers what to expect for each migration path, including the switch from Workwize to Rayda and switch from Hofy to Rayda.

If you are switching from Hofy and coverage in emerging markets was the driver, this comparison of Hofy alternatives for emerging market coverage covers how the options stack up. For anyone evaluating the switch from Workwize, this breakdown of Workwize alternatives is worth a look before you commit.

One note on Deel IT specifically: if cost was part of the reason for switching, the full cost breakdown of equipping remote employees globally shows where the savings add up across hardware, shipping, and customs fees.

What Post-Migration Steps Should You Take in Week 3?

Week 3 is not part of the 14-day switch to Rayda, but it is where the gains get locked in. The main tasks are device refresh planning, retrieval workflow setup, and confirming your MDM policy coverage across all regions.

The post-migration period is when most teams discover the things their previous vendor was quietly not doing: devices sitting untracked, retrieval requests going nowhere, no audit trail for end-of-life disposals. Rayda's portal surfaces all of this, which can feel like finding problems. You are not finding problems. You are finally being able to see them.

Here is the post-migration checklist:

For teams thinking about longer-term device planning, this guide to planning a 3-year device refresh cycle covers how to structure it without chaos when you are managing devices across multiple countries.

Understanding device lifecycle management as a full framework, not just procurement, is also worth doing in week 3. It changes how you think about retrieval, wiping, and redisposal from the start.

FAQ

How long does it take to switch to Rayda from another vendor?

Switching to Rayda takes 14 business days when following the structured migration plan. The timeline covers inventory audit (days 1–3), parallel operations setup (days 4–6), MDM and HRIS integration transfer (days 7–10), and full cutover with validation (days 11–14). Teams with clean inventory data and straightforward MDM setups sometimes complete faster.

Will there be any downtime during the migration to Rayda?

No. The plan uses a parallel operations window (days 4–10) where both your old vendor and Rayda are active simultaneously. No new hires are blocked, and no devices go unmanaged during the transition. Cutover only happens after every active device has been validated in Rayda's system.

Does Rayda handle the migration or do I have to manage it myself?

Rayda's migration team manages the heavy lifting. Your IT lead provides inventory data, grants HRIS access, and signs off at each phase milestone. Rayda handles portal setup, MDM environment configuration, gap analysis, and integration testing. Most customers report less than 4 hours of total internal IT time across the 14 days.

Can I migrate some devices to Rayda first and others later?

Yes. The device management migration plan is designed around cohorts precisely for this reason. You can migrate by region, by device type, or by business unit. Teams that are hiring actively in a new market often migrate that region first to capture Rayda's faster local sourcing before completing the full migration.

What happens to open orders with my current vendor during the switch?

Open orders already in production or in transit with your current vendor are allowed to complete. Orders not yet fulfilled are reviewed on day 10 and redirected to Rayda where possible. Your migration lead documents every redirect decision. No order falls through without a documented resolution.

Does Rayda integrate with my existing MDM and HRIS tools?

Yes. Rayda integrates with major MDM platforms (Jamf, Intune, Kandji, Mosyle) and common HRIS tools including Workday, BambooHR, HiBob, and Rippling. Integration setup happens in days 5–6 of the migration, with auto-provisioning going live on day 9 after a confirmed test sync.

What if I have devices in transit with my current vendor during migration?

Devices already in transit with your current vendor during the migration stay under that vendor's logistics until delivery is confirmed. They are then enrolled into Rayda's MDM on arrival. In-transit devices are tracked separately in the gap report produced on day 3, so nothing is unaccounted for.

If your team is managing devices across multiple countries and your current vendor is slow, expensive, or missing coverage where you are hiring, Rayda handles procurement, deployment, tracking, retrieval, and disposal across 170+ countries, usually within 8–12 days. Start your 14-day switch with a single call. Book your migration kickoff call today and Rayda's team will build your custom transition plan from day 1.