Back to blog
Network & Infrastructure·

Office IT Relocation in Bangalore: The Checklist That Decides Your Date

IT technicians de-installing network equipment from a server rack during an office IT relocation in Bangalore

The number that decides your move date

Forty-one days. That is what an Airtel Business leased line actually took for a 90-seat office moving from Koramangala to an ORR building near Bellandur in early 2026 — from signed form to green link light. The lease was signed on 4 January. The tenant wanted to occupy on 1 February. The circuit came up on 14 February.

They paid double rent on two floors for eleven days. At ₹2.1 lakh per month per floor, that is roughly ₹77,000 in avoidable rent, plus ₹18,000 in wasted shift allowances for the crew that showed up to a building with no internet. The movers, the furniture, the painting, the biometric doors — all of it was ready. The link was not.

I have run or supervised around thirty office IT relocations in Bangalore since 2014. The single most reliable predictor of whether a move goes smoothly is not the quality of the packing, or the rack diagram, or how many people show up on Saturday. It is how many weeks before the target date someone placed the ISP order. Everything else in this checklist can be compressed if you throw people at it. ISP provisioning cannot. It is the critical path, and almost every relocation plan I see treats it as a footnote.

This is the working checklist our team uses, with the lead times, prices and failure modes that actually apply in Bangalore in 2026.

The twelve-week skeleton

Before the detail, here is the shape of it. Print this if you want.

Weeks before moveWhat must be doneOwnerWhy it slips
12Site survey of new premises; check what cabling, power and fibre already exist; confirm landlord permissionsIT + FacilitiesBuilding not yet handed over, or landlord wants a formal NOC letter
10-11Order primary and secondary ISP circuits; order static IPs and DNS delegationITSkipped because "we'll do it after we sign the lease"
9-10Full asset audit: every device, serial, warranty, MAC, and whether it moves at allIT + FinanceNobody owns the old asset register
8Finalise rack design, patch panel numbering, cable schedule for new officeIT/Network vendorWaiting on the ISP demarcation point
6-7Order new passive cabling and any new switches, APs, firewallsProcurementLead time on networking gear from distributors
4-5Stage the new office network: firewall config, VLANs, DHCP/DNS, test with temporary linkITTrying to do it all on cutover weekend
2-3Build the cutover runbook; brief every owner; confirm ISP activation dates in writingIT leadNobody wrote the runbook
1Freeze non-essential changes; confirm movers, lift bookings, building access for the SaturdayFacilitiesLift not booked for the heavy rack
0 (cutover weekend)De-install, transport, re-rack, power-on, test, hand backEveryoneA single missing SFP module
+1 weekHypercare: on-site engineer, daily checks, close-out auditITDeclared victory too early

Most teams I meet run this as a six-week plan. It can be done in six weeks if the new building already has a working ISP circuit you can take over, or if you can survive on 4G/5G failover for a fortnight. If neither is true, you are planning a six-week project and hoping.

The ISP provisioning lead time, told honestly

This is where I will be blunt, because polite versions of this advice cause real losses.

A new fibre circuit in Bangalore — leased line or enterprise broadband — needs a physical path from a service provider's nearest available node to your building, then into your server room. That path involves: a feasibility check against the building address, a landlord or builder NOC, trenching or overhead cabling in some cases, a fibre pull to your floor, termination at an ONT or media converter, and then provisioning the logical circuit. Each of those steps has its own queue.

In 2026, realistic lead times from order to live circuit, for a commercial building in Bangalore:

Provider typeTypical lead time (2026)Range you should plan forNotes
Airtel Business leased line (new building, no prior circuit)30-45 days25-75 daysWorst case when the building has no existing Airtel fibre
Jio Business leased line (new)25-40 days20-60 daysFaster where Jio already has a node in the building
ACT Enterprise (new)15-25 days12-40 daysStrong in many Bangalore tech corridors, thinner elsewhere
Existing circuit transferred or re-terminated (same building)5-10 working days4-15 daysThe easy case — almost always worth checking first
Secondary/backup link on a different provider20-35 days18-50 daysDo not assume it arrives with the primary

Two practical rules from this table.

First, always ask the building's facility manager whether the premises already have a working circuit from any provider, and from which ones. A building that has an Airtel fibre already pulled to the floor can cut six weeks off your plan. A building that has none, in a lane off a minor road, can add them.

Second, never order a single circuit and call it done. Order the primary early, and order a secondary on a different provider — Airtel plus ACT, or Jio plus Airtel — no later than two weeks behind the primary. On cutover weekend, if the primary is not up, the secondary is your whole business. If both are down, your team is on 5G dongles and hotspot tethering, and your cloud apps will crawl.

You also need to order static IPs and, separately, get your public DNS records ready to point to the new addresses. That DNS change has a TTL. Lower the TTL on your public records (mail, VPN, any published services) to 300 seconds at least 72 hours before cutover. Otherwise the old IP stays cached at your users' resolvers and at your partners' mail gateways for hours after the link is live.

Asset audit: the part everyone skips and everyone regrets

The asset audit is not a spreadsheet exercise for the finance team. It is the working document that drives the rack plan, the procurement list, the disposal register and the GST paperwork. Do it properly once and four other problems disappear.

For every IT asset in the old office, capture:

  • Asset tag and serial number
  • Make, model, and where relevant the specific revision (a Dell PowerEdge R640 vs R650 matters for rail kits)
  • Purchase date, warranty end date, AMC or support contract number
  • Physical location and owner (user, department, or rack position)
  • MAC address, and for servers, the hostname and IP
  • Whether it moves, gets retired, gets sold, or gets scrapped

That last column is the one that saves money. In a typical 100-seat Bangalore office I would expect to find:

  • 8-15% of desktops and laptops that are past warranty, not assigned to anyone, and not needed at the new site
  • 2-4 servers running something nobody can identify (often an old file share or a Tally or ERP application server)
  • A stack of switches and APs still in the rack that were replaced two generations ago and never removed
  • Printers that are cheaper to replace than to move and re-commission

The disposal route in India matters. Old IT assets, especially anything with a battery or a screen, should go through a registered e-waste handler and you should get a certificate. Under the E-Waste (Management) Rules, 2022, bulk consumers — which includes most companies above a modest size — have recordkeeping obligations. If your finance team has been depreciating these assets, the disposal also needs to hit the books correctly. A clean asset register with serials is what lets your CA write off the right things.

And GST: if you sell the retired kit to a refurbisher or a reseller, that is a taxable supply and needs a proper invoice with GST. If you scrap it, keep the e-waste certificate and the internal approval. Auditors in 2026 are noticeably more careful about IT asset disposal than they were five years ago.

Rack de-install: the Sunday that breaks things

Here is where relocations actually go wrong. The rack looks orderly. Someone labels three cables and assumes the rest are fine. On the Monday after the move, the ERP is unreachable and the CCTV recorder has no network, and nobody remembers which port on which switch fed which VLAN.

Do this instead.

Before you touch a single cable

  • Photograph the front and back of the rack, top to bottom, in overlapping frames. Then photograph each patch panel.
  • Export the running config from every switch, router, firewall and AP controller. FortiGate, Cisco, Aruba, Ubiquiti, Sophos — all of them have an export. Do it to a USB drive and to your cloud storage.
  • Take a port-by-port record: switch port number, patch panel port, room, wall port, device. A spreadsheet is fine; a photo of a handwritten sheet is not.
  • Note the exact firmware versions on every device. If you are also doing a firmware upgrade during the move, stop. Do not change two things at once.
  • Note the IP addressing scheme, VLAN IDs, DHCP scopes, DNS servers, and the WAN static IP block.

The de-install itself

  • Power down in order: application servers, then database servers or the NAS, then hypervisor hosts, then storage, then switches and firewall. Your Synology or QNAP NAS should be shut down through its own interface so the RAID metadata is clean — pulling the plug can cost you a rebuild on the other side.
  • Label both ends of every cable you intend to reuse. Colour-code by function: one colour for user data, one for voice, one for uplinks, one for management. This sounds fussy and it saves hours.
  • Remove drives only if security policy requires it for transport (some regulated clients do). Otherwise leave them in and transport the whole unit in a padded crate, not loose in the back of a Tata Ace.
  • The rack itself: if it is a 42U four-post cabinet, it does not go in the lift unless the lift is booked and the cabinet is split or moved on its side. Confirm with the building's facility team weeks in advance. A rack stuck in a lobby on Saturday morning is a very expensive Sunday.
  • Batteries for UPS units are heavy and should be handled separately. Note the model — an APC Smart-UPS SRT 5000 or similar — and check whether the batteries are due for replacement anyway. Moving a UPS with 4-year-old batteries is a good moment to replace them.

Transport

Bangalore-specific: the ORR and the airport road are unpredictable at the best of times, and a monsoon afternoon can turn a 40-minute drive into two hours. Book the transport for early morning on the Saturday, not afternoon. Use a vehicle with a closed body for servers and networking gear — dust in a Bangalore summer is real, and a sudden shower in June or September is very real. Pad and strap the rack. Never let a cab or an auto carry a server.

The cutover weekend runbook

This is the document that decides whether Monday happens. It should fit on two pages and be readable at 11pm by someone who is tired.

A worked example from a 120-seat relocation we handled in March 2026, moving from an office near MG Road to a building on Old Madras Road:

Friday evening (T-1)

  • 18:00 — Final business-day checks; confirm the new office circuits are green (both primary Airtel and secondary ACT); confirm remote access to the new firewall's management interface from outside.
  • 19:00 — Announce mail from IT to all staff: "From 18:00 Saturday, all office systems offline. Email continues via Microsoft 365 (cloud) throughout. Do not come to the office over the weekend." This is done because your mail is in the cloud and your file shares may not be; set expectations exactly.
  • 20:00 — Take a final full backup of on-prem file servers and the Tally/ERP database. Verify the backup by test-restoring one file. A backup you have not tested is not a backup. Veeam Backup & Replication v12 with a restore verification is fine; a copy on a USB drive with no check is not.

Saturday (T-0)

  • 08:00 — Team on site at old office. Confirm all users are logged off. De-install begins.
  • 08:30-12:00 — Rack teardown, cable labelling, server power-down, crating.
  • 12:00-13:00 — Transport departs. Move crew follows.
  • 13:30-18:00 — New office: rack into position, power distribution units connected, patch panels terminated to the new structured cabling, switches and firewall racked.
  • 18:00-21:00 — Power on: switches first, then firewall, then storage, then hypervisor hosts, then application servers. Verify each layer before moving up.
  • 21:00-23:00 — Bring up the WAN — confirm both circuits, verify the firewall policy has been loaded from config, verify DHCP and DNS, verify VPN tunnel for remote staff.
  • 23:00 — First smoke test: can you reach the internet, can you reach the ERP, can a test laptop on the user VLAN reach the file share, can you receive mail.

Sunday (T+1)

  • 09:00-12:00 — Reconnect user access points, verify wireless coverage; walk the floor with a laptop and a phone.
  • 12:00-16:00 — Restore or re-point any services that had to be re-IPed; test printers, scanners, biometric readers, CCTV recorder.
  • 16:00-18:00 — Full test pass: new users can log in, VPN users can log in, mail flows, phones work, backup jobs scheduled against new storage paths.
  • 18:00 — Go/no-go decision. If something is broken, it is far better to declare Monday a work-from-home day (for roles that can) than to have 120 people standing in a lobby at 9:30am.

Monday (T+2)

  • On-site engineer from 08:00. Hypercare for the week.

The failure story

A 60-seat office we were called into after the fact, in November 2025, did not do this. They planned the move in five weeks around the lease date. The new building's landlord had promised the ISP "would be sorted". On the Saturday, the rack went in, servers came up, and there was no internet — the Airtel circuit had a feasibility issue with the building's fibre path and would not be live for another 17 days. The team spent Saturday night fighting it. On Monday, 60 people arrived at a building with no connectivity. The 5G backup (a single Jio dongle) choked under load. They lost effectively two working days. At an average fully-loaded cost of about ₹3,500 per person per day, that is ₹4.2 lakh of productivity, before counting the customer-facing delays and the fact that their CEO spent Monday morning on a hotspot.

They then paid us to do what should have been done in week two: order an alternate ACT circuit (which, because ACT already had a node in the building, was live in 9 days), set up a proper SD-WAN failover, and rebuild the runbook. The fix, in total, cost them roughly ₹1.1 lakh in labour and equipment plus the 9 days of the interim links. Both numbers together are still less than the two lost days — but both would have been zero if someone had called the ISP in week ten instead of week four.

What actually needs to move, and what should not

The most successful Bangalore relocations I have handled are the ones where the move was treated as a chance to leave things behind. Every rack you empty and every server you retire reduces the number of things that can fail on the Saturday.

A quick decision table for common items:

ItemMove?If not, what2026 cost of the alternative
On-prem file server (5+ years old)Usually noMigrate to SharePoint/OneDrive or a NASSharePoint is in your Microsoft 365; NAS from ~₹55,000 for a Synology DS923+ with drives
Tally / ERP serverYes, if on-premRe-IP carefully; or move to cloud hostingCloud hosting from ₹8,000-₹25,000/month depending on size
8-year-old desktopsNoBuy refurbished or newNew business desktop ~₹32,000-₹45,000
Printers with no service contractOften noNew MPS contract₹1,200-₹3,500 per month per device
Old switches (100Mbps, unmanaged)NoNew managed PoE switches~₹18,000-₹45,000 per switch
Firewall that is out of supportNoNew NGFWFortiGate 90G street price around ₹1.1-1.4 lakh
CCTV NVR and cameras under 3 yearsYesRe-point to new networkReplacing a 16-channel NVR and 16 cameras would be ₹1.5-₹3 lakh
UPS with batteries over 4 yearsMove the UPS, replace batteriesNew batteries at new site₹18,000-₹40,000 depending on capacity

That last row is the one that catches companies out. Moving a UPS with tired batteries is a chance to arrive at the new office with a power problem. Replace batteries at the new site, and test the auto-switchover before everyone arrives on Monday.

Bangalore power deserves a word. Cauvery and BESCOM supply is generally decent but not uniform — some ORR buildings have generator backup, some do not, and some have a generator that is only wired to the lifts and emergency lighting. Before you sign the new lease, confirm what the building provides: DG backup to your server room, or just common areas. If the DG does not reach your rack, you need a UPS sized for at least 20-30 minutes of runtime, and you need to test it under real load, not estimate it. A 3kVA UPS with a 5-minute runtime at full load is not enough time for a graceful shutdown of a hypervisor and three VMs.

The stuff people forget until Monday morning

A list, because it is genuinely a list.

  • Biometric and access control. Your new building's access control is likely managed by the landlord. Your payroll or attendance system may need its own device. These often need network ports and IP addresses. Make sure they are in the plan, not discovered on Monday.
  • CCTV. The NVR is probably on the IT network. New cabling, new switch ports, new IP range. Test all cameras from the NVR before the week starts, not from a browser one at a time.
  • Phone system. If you are on an on-prem IP PBX (Asterisk, 3CX, or a hosted 3CX for SMEs), confirm the SIP trunks will work from the new IP. Many SIP providers restrict by public IP — a new static IP needs a trunk reconfiguration at the provider, and that is not a Saturday-night task. Move it to week minus two.
  • Printer and scanner drivers. IP addresses change. DHCP reservations are your friend, but you need a plan to push new addresses to user machines. Group Policy or your MDM handles Windows; Macs may need manual work.
  • Door signage and delivery address. Change the delivery address in your e-commerce, invoice, GST and courier accounts. Otherwise your new server's rail kit goes to the old building.
  • Regulatory records. If you hold client data under a contract or under CERT-In directions (the 6-hour incident reporting norm is the relevant bit here only if something breaks), confirm your security log retention is intact across the move. Do not lose 180 days of logs because you wiped an old firewall.
  • DPDP. Under India's Digital Personal Data Protection Act framework, your records of where personal data lives should survive the move. If you are retiring a server that held customer data, confirm the disposal includes verified media sanitisation, not just a format.

When to bring in a specialist, and when not to

I will be honest about where our own service is and is not the right fit.

Bring in a specialist IT relocation partner if: you have more than 50 seats, you have an on-prem server room with more than a couple of hosts, you have regulatory obligations around data, you do not have a dedicated network engineer who has done this before, or your move is under six weeks away.

Do not bring in a specialist if: you are 15 people on laptops, everything you use is in Microsoft 365 and a cloud CRM, and your total on-site IT is a switch, a firewall and a printer. In that case, do it yourself with a clear checklist and a Saturday. Paying a relocation partner for that is wasteful.

For the middle case — most 20-200 seat Bangalore offices — we usually recommend a fixed-scope engagement: we do the audit, the ISP coordination and the weekend cutover, and your team handles the day-to-day. If you want to see how we structure that, it sits inside our managed services offering, and you can talk to us about your date once you have even a rough target.

Costs, in real numbers

For a 50-user office moving within Bangalore in 2026, a realistic budget range:

ItemLowHighNotes
New passive cabling (50 seats)₹65,000₹1,40,000Depends on whether new building has any cabling
ISP setup (new leased line)₹15,000₹45,000Installation + first month, varies by provider and speed
Network gear refresh (if needed)₹0₹3,50,000Firewall ₹1.1-1.4 lakh, 2-3 switches, APs
Rack relocation and de-install₹40,000₹1,10,000Labour, transport, reinsurance of config
Cutover weekend engineer time₹35,000₹80,000Two engineers, Sat-Sun
Asset audit and disposal₹15,000₹45,000Includes e-waste certificate
Hypercare week₹20,000₹50,000On-site days 1-5
Total₹1.9 lakh₹8.2 lakhRange is wide because scope is

For a 200-seat office, multiply the mid-point by roughly 2.5-3x, not 4x, because the fixed costs amortise.

As a same-building or same-campus move, cut the cabling and ISP lines out and you are looking at ₹60,000-₹1,80,000. Those moves are the ones worth doing yourselves with a checklist.

FAQ

How long before the move should I order the ISP circuit in Bangalore?

Ten to twelve weeks before the target occupation date, for a new building with no existing circuit. If the building already has a working circuit from a provider you can use, five weeks is enough. Order a secondary circuit from a different provider no later than eight weeks out, even if you think you will not need it.

Can I run the cutover on a Saturday and have everyone working Monday?

Yes, for offices up to about 100-150 seats with well-documented configs and a staged new office. The key is to stage the new network on the previous weekend using a temporary link, so the cutover Saturday is mechanical. Above 150 seats or with multiple sites, plan for Monday as a work-from-home day as a hedge.

Do I need to move my on-prem servers or can I move to cloud during the relocation?

If you were going to migrate anyway, do it four to six weeks before the move, not during it. Migrating and relocating in the same weekend doubles the failure surface. Migrate first, confirm for two weeks, then move the remaining hardware.

What about GST on the relocation services and new equipment?

Relocation services from a vendor are a service and attract GST at 18%. New equipment carries GST at the applicable rate (18% for most IT hardware). If you are GST-registered, you claim input credit; if you are not, budget the GST into your project cost. Make sure the vendor raises a proper tax invoice with your GSTIN — relocation is one area where informal quotes are common and get messy at audit.

How much downtime should I plan for?

Aim for a weekend: about 24-30 hours for a 50-100 seat office. Actual downtime for users is usually the two weekend days plus, in a bad case, Monday. Anything more than a weekend of user downtime means the plan was thin. The work itself is more like 60-100 person-hours, mostly preparation.

Do I need to notify anyone if I hold client data and the office moves?

Under most client contracts, yes — your registered address changes, and some clients require notice before a change in data location. Review your contracts. This is also the moment to review your DPDP records for where personal data lives, and to confirm the disposal of any retired storage is documented.

Your next concrete step

Open a calendar and work backwards from your target Monday. Count 75 days backwards and put a meeting on that date labelled "ISP order must be placed." If that date is in the past, you have a problem to solve this week, not next month.

Then call the new building's facility manager and ask one question: "Which ISPs already have fibre into this building, and can we get a circuit from any of them without a new pull?" The answer decides whether your project is a five-week job or a twelve-week one, and everything else in the plan hangs off it.

If you want a second set of eyes on the plan before you commit to a date, our managed services team has done this enough times in Bangalore to spot the problem in a fifteen-minute conversation. Get the date right and the rest is work.