MAM rollout and a 7.2 PB storage migration
Leads a ~7.2 PB NY→LA migration and Iconik MAM rollout, after negotiating the implementation SOW from $400K+ down to ~$201K.
Key outcome
$400K+ → ~$201K SOW · ~7.2 PB in motion
Executive summary
Leads a ~7.2 PB NY→LA migration and Iconik MAM rollout, after negotiating the implementation SOW from $400K+ down to ~$201K.
Situation
Two large libraries (~3 PB each) plus ~900 TB of spinning disk needed to consolidate from New York to Los Angeles, alongside a new MAM to make assets searchable and governable.
Challenge
Petabyte-scale migrations are unforgiving: limited bandwidth, a hard deadline, and zero tolerance for losing or corrupting masters — all while standing up a new MAM in parallel.
My role
Nick is both the business owner and the technical lead for the migration and the MAM rollout.
Actions
- 01Selected IMT Global over CHESA and negotiated the SOW from $400K+ to ~$201K.
- 02Designed the transfer plan using Aspera at ~5 Gbps across the two libraries.
- 03Stood up Iconik MAM as the unified asset and metadata layer.
- 04Sequenced the migration against a hard October 2026 deadline.
Systems involved
Results
- MAM implementation cost cut roughly in half through vendor selection and negotiation.
- A ~7.2 PB migration sequenced and underway toward the 2026 deadline.
- A single searchable, governable asset layer replacing scattered storage.
Transferable value
Large infrastructure programs need one person who owns both the contract and the implementation. That dual ownership is what keeps cost, risk, and timeline aligned.
Related skills