Price the Exit Before You Renew Colocation
A colocation renewal can look reasonable right up until you ask what it would take to leave.
The monthly cabinet and power rate may be competitive. Service may be acceptable. The account team may even offer a discount for another long term. None of that tells you whether the company can move its equipment, replace its connectivity, remove cross-connects, schedule technical labor, meet the notice requirement, and finish before the next billing period starts.
That work is your real renewal leverage.
Price it before you sign. If the exit is too expensive or too slow to execute now, another renewal usually makes the dependency stronger.
Start with the decision, not the quote
A colocation renewal should resolve one of four decisions:
- Renew the current footprint because the facility, services, risk, and economics still fit.
- Renew with corrected commercial or exit terms.
- Reduce the footprint and keep only the infrastructure that still belongs there.
- Start a migration and use a short extension or negotiated transition period to finish it safely.
The provider’s proposal does not answer that decision. It prices the services the provider already bills.
Your renewal record needs to connect the contract to the physical environment, network dependencies, applications, equipment, owners, and work required to stay or leave.
If the broader infrastructure strategy is unsettled, review when colocation still makes sense compared with cloud before turning a renewal into a default architecture decision.
Build one renewal inventory
Do not start with a cabinet count. Build one row for every billed service and every important dependency attached to it.
| Item | Evidence to collect | Decision to make |
|---|---|---|
| Cabinet, cage, or suite | Order form, location, capacity, access record | Keep, reduce, expand, or exit |
| Power | Committed and measured power, circuit records, overage terms | Right-size or retain |
| Cross-connect | A-side, Z-side, carrier, circuit ID, port, monthly charge | Keep, replace, or disconnect |
| Network service | Carrier order, term, demarcation, IP requirements, routing dependency | Migrate, renew, or redesign |
| Remote hands | Rate schedule, minimum charge, included hours, response process | Budget and support requirement |
| Hardware | Asset ID, owner, age, warranty, rack position, data classification | Move, replace, wipe, sell, or dispose |
| Access | Authorized people, badges, escorts, shipment rules | Update or close |
| Support | Monitoring, patching, backup, managed service, escalation owner | Retain, replace, or bring in-house |
| Contract obligation | Term, notice, removal duty, restoration requirement, fee | Accept, change, or escalate |
The invoice shows what the provider charges. It does not show which application breaks if a cross-connect disappears or who can approve the removal of an old storage array.
Reconcile the provider inventory against network diagrams, asset records, carrier records, support contracts, backup documentation, and the people who operate the workloads.
Anything without a credible owner goes into an exception queue. Do not carry an unexplained service into another term because nobody had time to investigate it.
Price the work nobody puts in the renewal quote
The cost of leaving colocation is not one migration line item. It is a stack of provider fees, replacement services, technical work, business risk, and overlapping bills.
Create a cost model with at least these sections.
Facility and provider charges
Use the current agreement, order forms, service guide, and rate schedule to identify:
- Early termination or minimum commitment exposure
- Required notice and the accepted notice method
- Cross-connect disconnect charges
- Remote-hands labor and minimum billing increments
- Shipping, receiving, staging, escort, and after-hours charges
- Deinstallation, cleanup, cabinet restoration, or abandonment obligations
- Access charges during the transition
- Final metered power, overage, tax, and pass-through charges
- The date recurring billing actually stops
Do not rely on a salesperson’s estimate for contract obligations. Trace each assumption to the signed terms or get the clarification added to the renewal record.
Replacement and migration costs
Leaving one facility usually creates work somewhere else. Price the destination before treating the current provider as expensive.
Include replacement colocation, cloud resources, new hardware, carrier installation, diverse connectivity, IP or DNS changes, security controls, backup changes, monitoring, implementation support, application testing, and internal labor.
Budget for overlap. Old and new environments may need to run together while the team replicates data, tests applications, changes routing, moves equipment, and proves rollback.
A proposal that shows the destination’s monthly run rate but ignores overlap and migration labor is not a usable comparison.
Hardware disposition
Every device needs a disposition before the move window opens:
- Move it to the new facility
- Replace it and migrate the workload
- Keep it temporarily for rollback
- Sanitize it and return it to a lessor
- Sanitize and resell, recycle, or destroy it
- Leave it only under a documented arrangement that transfers ownership and responsibility
Confirm who owns each asset and what data it may contain. Match the disposition method to company policy, contractual requirements, and the sensitivity of the data. Keep chain-of-custody and completion evidence where the risk requires it.
“We will figure out the old hardware later” is how equipment stays in a billed cage after the application has moved.
Business interruption exposure
Estimate the business impact of a failed move, not just the cost of the change window.
Which applications have a tested rollback? How long can each service be unavailable? What happens if the carrier circuit misses its delivery date? Who can stop the migration? Who owns customer, employee, and executive communication if the change affects service?
This is not a reason to renew automatically. It is a reason to build a migration plan that leadership can approve honestly.
Test the timeline against the contract
A migration plan can be technically sound and still miss the commercial deadline.
Put these dates on one calendar:
- Auto-renewal or nonrenewal notice deadline
- End of current term
- Latest date to order replacement connectivity
- Destination readiness date
- Hardware procurement and delivery dates
- Application migration and testing windows
- Change freeze periods
- Cross-connect and carrier disconnect dates
- Physical removal window
- Final inspection or restoration deadline
- Last expected invoice and dispute window
Work backward from the date the provider must accept the space as vacated, not from the date the application team expects to finish.
A move that completes one day before contract expiration leaves no room for a failed test, delayed shipment, rejected removal request, or unexpected restoration work.
Use an IT contract renewal calendar to track the notice event separately from the operational move. Missing either one can create another billing term.
Negotiate the exit while the provider still wants the renewal
If staying is the right decision, use the renewal to remove avoidable exit risk.
Ask for written clarity on:
- The exact notice deadline and permitted delivery method
- Which services terminate with the primary colocation order and which renew separately
- The process and charge for disconnecting cross-connects
- Remote-hands rates, response expectations, and after-hours treatment
- Access rights during migration and after notice is given
- Shipping, receiving, staging, and escort rules
- Hardware removal, abandonment, and disposal responsibilities
- Restoration standards and who decides the space is acceptable
- Final billing dates for space, power, network, and ancillary services
- Transition support and any required professional-services scope
- Price protection for a short extension if the migration slips
Do not ask only, “Can we leave?” The contract may allow termination while the operating rules make an orderly exit expensive.
Also separate the terms. Space, power, network, managed services, and carrier circuits may have different order forms, renewal dates, and termination requirements. One nonrenewal notice may not stop every charge.
Compare four scenarios on the same page
Leadership should see more than stay versus go.
Build a decision page with four scenarios:
| Scenario | Commercial view | Operating view | Exit view |
|---|---|---|---|
| Renew as proposed | Full term cost and escalators | Current support and capacity | Exit becomes later work |
| Renew with changes | Corrected footprint, rates, and terms | Required operational fixes | Better notice, transition, or extension terms |
| Reduce footprint | Remaining services plus consolidation work | Capacity and resilience after reduction | Partial removal and disconnect cost |
| Migrate | Destination, overlap, migration, and final charges | Staffing, testing, rollback, and support | Defined completion evidence |
For each scenario, show cash cost, internal labor, business risk, owner, deadline, unresolved assumptions, and the evidence required for approval.
Do not pretend every number will be exact. Mark estimates as estimates. The point is to expose the missing work before a contract term hides it again.
Know when renewal is still the right call
Renewal can be the smart decision when the workloads still fit colocation, the facility meets current requirements, connectivity and support are working, pricing is competitive, and the exit terms are manageable.
It can also be reasonable when a migration is strategically correct but cannot be completed safely before expiration. In that case, negotiate the shortest practical bridge with clear scope and pricing instead of signing a long term because the project started late.
Push harder when:
- The footprint includes hardware or services with no owner
- Committed power or space no longer matches need
- Cross-connect records conflict with carrier or network records
- The provider cannot explain final billing and removal requirements clearly
- A long term is required before the infrastructure strategy is complete
- A migration depends on one person, one carrier date, or an untested rollback
- Separate services have renewal terms the proposal does not show
Those are decision gaps. A discount does not close them.
Make exit evidence part of the final approval
Before approving the renewal, require a small evidence packet:
- Current service and asset inventory
- Signed agreement, order forms, amendments, and rate schedules
- Stay, reduce, renegotiate, and migrate cost comparison
- Contract and migration timeline
- Network and application dependency map
- Hardware disposition list
- Migration owners, testing plan, and rollback authority
- Written provider answers for unresolved exit charges and procedures
Then choose the decision and record why.
Renew if it still fits. Renegotiate if the service fits but the terms do not. Reduce if the footprint is larger than the requirement. Start migration if the environment or relationship no longer earns another term.
A good colocation renewal is not the cheapest cabinet rate. It is a decision the company can defend, operate, and reverse without discovering the exit plan after the signature.
If your colocation agreement is approaching renewal, request a Contract and Spend Risk Review. Bring the agreement, order forms, invoices, service inventory, network diagram, asset list, rate schedule, and current proposal. Catch Advisors will help you price the stay, the changes, and the exit before another term makes the decision for you.