Start planning 12 months before your 36-month colocation lease expires, and send written non-renewal notice before the deadline in your MSA (typically 60 to 180 days out) or you risk an automatic renewal. Move to IDACORE Boise on a 12-month term at $300/kW/month, billed on power draw, and overlap only what you're actively migrating.
Why Does Exit Timing Matter More Than the Move Itself?
Physically moving servers is the easy part. You rack them, cable them, bring them up, and verify. Anyone who's done a few migrations can plan that in an afternoon.
The contract is what bites you. A lot of three-year colocation agreements signed in 2023 are coming due in 2026, and most of them share the same traps:
- Evergreen clauses. Miss the notice window and the contract renews on its own, often for 12 months, sometimes for the full original term.
- Notice windows buried in the MSA. 60, 90, or 180 days before term end, delivered in writing, to a specific address. Email to your account rep often doesn't count.
- Renewal escalators. Annual increases of a few percent are common, and they compound if you roll over.
- Early termination fees. Usually the remaining monthly fees for the term. Leave six months early and you're paying for six months of space you don't use.
I've watched teams nail the technical plan and still eat a full extra year because nobody owned the calendar. Sound familiar? The fix is boring: put the notice deadline on a calendar the day you decide to move, assign one person to it, and get written confirmation back from your provider.
When Should You Start Planning a Colocation Migration to Boise?
Work backward from your term end date. Here's the timeline I'd use for a lease ending September 30, 2026:
| When | What to do |
|---|---|
| T-12 months (Oct 2025) | Pull the MSA. Find the notice window, renewal terms, escalator, and decommission obligations. |
| T-9 months | Measure real power draw on every server. Identify gear to retire instead of move. |
| T-7 months | Decide on IP strategy: renumber or bring your own ASN and space. Order any carrier circuits you need. |
| T-6 months | Send written non-renewal notice. Get confirmation in writing. Sign at IDACORE Boise. |
| T-3 months | Rack first wave in Boise. Stand up BGP sessions, test failover. |
| T-2 to T-1 months | Migrate workloads in waves. Shift traffic. |
| T-2 weeks | Final decommission at old site. Pull hardware, clear the cabinet, return badges. |
Six months of notice covers the strictest windows I've seen. If your contract says 90 days, you've got slack. If it says 180, you're right on the line, so don't let that step slip.
What Should You Measure Before You Give Notice?
Measure power draw, because at IDACORE Boise that's the number you pay for. Nameplate ratings on PSUs are useless for this. A server with dual 1100W supplies might pull 280W under normal load.
If your hardware has a BMC, grab readings over a week or two of normal traffic:
# Current, min, max, and average draw from the BMC
ipmitool -I lanplus -H <bmc-ip> -U <user> -P <pass> dcmi power reading
# Loop it across your fleet and log for a week
for host in $(cat bmc-hosts.txt); do
echo "$(date -Is) $host $(ipmitool -I lanplus -H $host -U admin -P "$BMC_PASS" \
dcmi power reading | awk '/Average power/ {print $(NF-1)}')"
done >> power-log.txt
Sum the averages and you've got a realistic kW figure. This step usually turns up something else too: the two boxes nobody's logged into since 2023. Retire them before the move, not after.
What Does the Move Cost Compared to Renewing?
Here's a scenario I see constantly. A Seattle-area SaaS company signed a 36-month lease for a full cabinet in 2023. The cabinet came with a 5 kW circuit, and they pay a flat monthly rate. Three years later, the cabinet holds ten servers, and measured draw is 2.8 kW. They're paying for a cabinet and a circuit sized for growth that never landed.
At IDACORE Boise, billing follows power draw regardless of rack space. 2.8 kW x $300 = $840/month for colocation. If they add a 1G transit commit at $600/month, the total is $1,440/month.
Compare that to what they'd sign at renewal. The left column below reflects typical market rates for a full cabinet on a 36-month term, not IDACORE pricing:
| Typical 36-month market lease | IDACORE Boise | |
|---|---|---|
| Term | 36 months | 12 months standard |
| Billing basis | Per cabinet or per circuit, flat | $300/kW/month on power draw |
| Smallest footprint | Half or full cabinet, often | 1U, no power commitment minimum |
| Monthly colo cost, this example | ~$1,800 (typical market rate, cabinet + circuit) | $840 (2.8 kW measured) |
| Renewal behavior | Auto-renewal clauses common | 12-month terms |
That's roughly $960/month back in this example, or about $11,500/year, before you touch bandwidth. And if they retire three idle servers during the move and drop to 2.2 kW, the Boise colo bill falls to $660/month. Under a flat cabinet rate, retiring servers saves you nothing.
The per-U angle matters here. IDACORE is the only provider in Boise that'll rent you a single rack unit. You're still billed on power, not the U. A single 200W server in 1U is $60/month (0.2 kW x $300). So if your consolidation leaves you with four servers instead of ten, you don't need to rent a cabinet you'll never fill.
What About the Overlap Period?
You'll pay for two sites at once for a month or two. There's no avoiding it. What you can control is how much of that overlap hurts. Because Boise billing tracks the power your gear draws, the new-site bill ramps up as each wave of servers comes online. It isn't a full second cabinet charge from day one. Plan 30 to 60 days of overlap and move in waves, not all at once.
How Do You Keep IP Space and Routing Intact During the Cutover?
This is where migrations quietly go sideways. Before you give notice, answer one question: who owns your IP addresses?
If your addresses belong to your current provider, they stay behind when you leave. You'll renumber into IDACORE-assigned space. Lower your DNS TTLs to 300 seconds a couple of weeks before cutover, run both address sets in parallel during the overlap, and audit every firewall allowlist, partner VPN, and SPF record that hardcodes the old IPs. Those allowlists are what break at 2 a.m.
If you have your own ASN and address space, you're in better shape. IDACORE runs IP transit from our own ASN with our own BGP peering. We've been doing this since we ran an ISP and peered at the Seattle Internet Exchange, and we don't resell somebody else's transit. You announce your prefixes to us, and we carry them.
The clean cutover is to announce from both sites at once, then shift traffic with AS-path prepending. Prepend at the old site so inbound traffic prefers Boise:
! FRR at the OLD site: make this path less attractive
route-map OLD-SITE-OUT permit 10
set as-path prepend 64500 64500 64500
!
router bgp 64500
neighbor 203.0.113.1 route-map OLD-SITE-OUT out
Watch traffic drain from the old site over a few days. When it's near zero, withdraw the announcement there and decommission. No flag day, no maintenance window where everything goes dark at once.
Transit at IDACORE is committed bandwidth billed at the 95th percentile, on-net at all locations:
| Commit | Monthly | Per Mbps |
|---|---|---|
| 100M | $170 | $1.70 |
| 1G | $600 | $0.60 |
| 10G | $2,000 | $0.20 |
| 100G | $11,050 | $0.111 |
If part of your stack also runs in a hyperscaler, this is where the math gets interesting. Per-GB egress grows with every customer you add and is nearly impossible to forecast. A 95th percentile commit is a number you can put in a budget and defend.
Boise also has seven on-net carriers: Zayo, Lumen/Level 3, Cogent, CenturyLink, Syringa, Cable One, and Hurricane Electric. If you need a private circuit back to an office or another site, order it at T-7 months. Carrier lead times are the one schedule item you don't control.
How Do You Avoid Locking Yourself Into the Next 36 Months?
The whole reason you're reading this is that a contract signed in 2023 made assumptions about 2026 that turned out wrong. Don't repeat it.
IDACORE Boise runs on 12-month standard terms. Enterprise providers typically want 36. A one-year term lines up with how most teams plan hardware refreshes and budgets, and it means your next exit decision is a calendar reminder, not a negotiation.
A few other things worth checking off before you sign anywhere:
- Compliance. IDACORE Boise is housed in a SOC 2 Type II certified facility that also holds PCI DSS, NIST 800-53, SSAE-16, and HITRUST CSF certifications. It's compliance-ready for HIPAA, financial, and government workloads. Send the reports to your auditor early.
- Latency. From Boise it's 23ms to Seattle, 22ms to Portland, and 14ms to Salt Lake City, with sub-5ms latency to Treasure Valley businesses. Test it from your users' networks, not just a looking glass.
- Second site. If the move is also your chance to add DR, IDACORE North in Coeur d'Alene uses the same $300/kW/month power pricing and sits about 45 minutes from Spokane.
- Support. When you call, you get operators who know your rack, not a ticket queue in another time zone.
Leaving a 36-month lease well comes down to the calendar more than the forklift. Get the notice in, measure your real power, decide your IP strategy early, and move in waves.
Frequently Asked Questions
How far in advance do I need to give notice to exit a 36-month colocation contract?
Check your MSA. Most colocation contracts require written non-renewal notice 60 to 180 days before the term ends, and many auto-renew for 12 months or longer if you miss that window. Start reviewing the contract 12 months out, send notice by certified mail or the method your contract specifies, and get written confirmation back. Missing the deadline by one day can cost you another full year at an escalated rate.
Can I rent a single rack unit of colocation in Boise?
Yes. IDACORE Boise offers per-U colocation with a 1U minimum and no power commitment minimum. You rent the single U, but you're billed $300/kW/month for the power your server draws, not a flat fee for the space. A server drawing 200W costs $60/month (0.2 kW x $300). That makes Boise a practical landing spot for small fleets consolidating out of a half or full cabinet.
Does IDACORE Boise require a 36-month colocation contract?
No. IDACORE Boise uses 12-month standard terms, while enterprise colocation providers typically require 36 months. Pricing is $300/kW/month billed on power draw regardless of rack space. A shorter term means your next exit window lines up with hardware refresh cycles and budget planning, instead of locking you in for three years based on capacity guesses you made at signing.
Can I keep my IP addresses when I move colocation providers?
It depends on who owns them. If your addresses are assigned from your current provider's allocation, they stay with that provider and you'll need to renumber. If you hold your own ASN and address space, IDACORE accepts your BGP announcements over IP transit from our own ASN, so you can announce from both sites during the overlap and shift traffic gradually with AS-path prepending before decommissioning the old location.
How much does IP transit cost at IDACORE Boise?
IDACORE prices IP transit on committed bandwidth with 95th percentile billing: 100M is $170/month ($1.70/Mbps), 1G is $600/month ($0.60/Mbps), 10G is $2,000/month ($0.20/Mbps), and 100G is $11,050/month ($0.111/Mbps). Transit is on-net at all IDACORE locations and runs on our own ASN and BGP peering. There's no per-GB egress billing, so your bandwidth bill doesn't spike when traffic grows.
If your lease ends in 2026, the notice deadline is probably closer than you think. Send us your measured power draw and your term end date, and we'll map out a cutover plan on a 12-month Boise term where you pay for the power your servers draw, not empty rack space. Get a Boise migration plan built around your contract dates.