Microsoft Mover

» see mover.io as it lived, on the wayback machine

~ the obituary ~

mover was a tool you needed if your company was switching from box or dropbox over to onedrive. that was never my problem. i worked on small teams and pet projects where the cloud-storage choice was set on day one and never revisited. mover.io existed for the it admin who got handed a 40-terabyte sharepoint migration and a six-week deadline.

the company started in edmonton around 2012 as an independent saas. eric warnke ran it. the product was a web app you logged into, connected your source bucket and your destination bucket on either end, and watched a progress bar count down the gigabytes. it supported box, dropbox, google drive, egnyte, amazon s3, and about ten other source platforms. the value was that it handled the metadata edge cases that always blew up in-house migration scripts.

microsoft acquired mover on october 21 2019 as part of the rajesh jha era push to convert office on-premises customers to microsoft 365. the announcement was made by jeff teper on the official microsoft blog. terms were undisclosed. the mover.io url stayed live, the brand stayed visible inside the sharepoint admin center, and the free tier remained available for self-service migrations under 100 gigabytes.

the wind-down came in two stages. enterprise migration features moved into the rebranded sharepoint migration manager throughout 2022 and 2023, with feature parity reached by early 2024. the consumer mover.io web app for individuals and students got a retirement notice posted in mid-2024 with a hard shutoff date of october 31 2024. the mover.io domain currently redirects into microsoft learn documentation for the replacement tool. the brand is dead, the original product is gone, the migration logic survives buried inside the sharepoint admin console.

~ the case file ~

~ the climb ~

mover.io's pre-microsoft product was one of the cleanest examples of the 2010s b2b saas pattern. small team, single problem, web ui, monthly subscription tied to the amount of data moved. they competed with cloudfuze and multcloud on the saas side and the bigger consultancies on the enterprise side. the moat was the per-provider api-handling code, which had to track box's permission model alongside google drive's shared-drive quirks for every customer.

microsoft's interest was specific. office 365 onboarding was the largest microsoft enterprise sales motion of the late 2010s, and the file-migration step was where customer projects stalled. buying mover.io was cheaper than building an equivalent in-house migration team from scratch.

~ the day it died ~

microsoft posted the mover.io retirement notice quietly inside the microsoft 365 admin center, not on the broader microsoft blog. the cutoff was october 31 2024 for the web app. enterprise customers were given migration paths to the sharepoint migration manager equivalent. individual and student users got nothing more than a redirect.

this is the standard microsoft acquired-tool-shutdown pattern. acquire the startup, run it in parallel for two or three years to maintain customer continuity, fold the working parts into the matching first-party microsoft product, retire the original brand with minimum public notice. wunderlist went through this when it became microsoft to-do, sunrise when it folded into outlook calendar. mover.io was the next one through the same door.

~ what it became ~

the sharepoint migration manager still runs. it handles the same migration workflows mover.io used to handle, with the same provider-coverage list, on the same azure infrastructure. it just looks like every other microsoft admin console now, which is to say a blue-and-white sea of dropdowns inside the microsoft 365 portal. mover.io's edmonton-startup ui personality did not survive the absorption.

@}-->--

              )
             (_)
            .-'-.
            |   |
            |   |
            |   |
            |   |
          __|   |__   .-.
       .-'  |   |  `-:   :
      :     `---'     :-'
       `-._       _.-'
           '""""""

« previous  ·  random  ·  next »