Coming from MediaSilo: what the Wiredrive move left behind

What the one-way migration did not carry across, what you are rebuilding by hand either way, and how the three MediaSilo share surfaces translate here.

If you arrived in MediaSilo through the sanctioned Wiredrive migration, you have probably already gone looking for something that is not there. The sync was one way and irreversible, and per MediaSilo's own migration documentation it did not carry over project trash, legacy project reports, legacy presentations, or asset-level approvals and comments. Wiredrive themes will not be carried over either. The legacy audit trail was not deleted, it was stranded: still sitting in Wiredrive, not in the tool you now work in.

MediaSilo is a real, video-native platform, actively maintained under EditShare, and none of this is an argument that it is not. This is a map of what the move cost, and an honest look at where the rebuilding can happen.

Your presentations have to be rebuilt either way

That is the hinge, so it is worth sitting with. Legacy presentations did not migrate, which means you are reconstructing them by hand whichever tool you land in. EditShare publishes a help article titled "Recreate Classic Wiredrive Presentation Styles in Spotlight", and the title tells you the shape of the job: the old styles get rebuilt in the new surface.

The work is the same size wherever you do it. So this is the one moment where looking at a second option costs you nothing, because the rebuild is on your list regardless. Rebuild in Spotlight and it may fit you perfectly. You are no worse off for having compared.

The vocabulary, translated

MediaSilo gives you three named share surfaces plus an analytics page. They line up like this:

• Review Links become review links: timecoded comments, drawing on the frame, approvals recorded per version, and no account for the person reviewing.
• Presentations and Spotlights land on two surfaces here. A branded page of video is a reel. A PDF or a PowerPoint you want read is a presentation.
• Insights becomes view analytics: who watched, how far they got, and how engaged they were.

The phone question

MediaSilo's documentation states: "At this time, mobile viewing is not supported for Spotlights or Presentations." Their Review Links are described as built for mobile, so this applies to the two presentation surfaces specifically.

Picture where that lands. A client opens your pitch on a phone, in a taxi, between two other meetings. That is a real share of first opens, and a first open is the one that decides whether there is a second. Every surface here is built to be opened on a phone.

What comes with rebuilding here

• Approvals attached to a version, so a Monday sign-off keeps pointing at the Monday cut rather than at whatever is newest. See Collect approvals on a cut.
• Gates on any link: a password, an expiry date, or an email capture before the video plays.
• Presentations with slide-level analytics, so you can tell which pages were read and which were scrolled past. See Read deck analytics slide by slide.
• Audience testing, which no other tool in this category offers: put two cuts in front of real recruited viewers and get a statistically honest read on which one landed. See How audience testing works.

Moving the library

The two Wiredrive guides carry the practical detail, and both apply whether you are moving now or moved a year ago: where your presentations live now covers rebuilding the pitch side, and review and approvals covers the feedback side, including what to save before you lose access to it.

If you are a native MediaSilo user with no Wiredrive history, none of the migration losses apply to you, and the honest comparison is narrower: the phone question above, and whether the review, pitch, and testing surfaces belong in one place. Start with which surface to use, build one reel, and send it on a real pitch.