Key takeaways
- A weekend IT move works for most small Dallas offices, but only if internet, cabling and the IT room at the new site are finished before Friday.
- The weekend itself is disconnect, transport, reconnect and test; none of the planning happens on the weekend.
- Servers and network equipment travel with the technician, not on the pallet with the desks.
- Sunday is a buffer, not a work day; if the plan needs Sunday to finish, the plan is too tight.
- After-hours rates apply to weekend work, and it is still usually cheaper than a weekday move that stops your office.
Can an office move its IT over a weekend?
Yes. For most small and mid-sized Dallas offices, the IT side of a move fits between Friday close of business and Monday morning, with no lost business days. I am Anthony Omini, the owner of Cross River Tech, and weekend moves are the normal way I run office relocations across Dallas–Fort Worth. Staff shut down on Friday, I disconnect and move the server and network gear that evening, reconnect at the new site on Saturday, and use Sunday only for what Saturday found.
The condition is that the weekend is only for moving. Everything that belongs to the new building, internet, cabling, the rack, the switch, the firewall, the Wi-Fi, has to be live before Friday. If any of it is not, the weekend becomes a construction project with a Monday deadline, and Monday loses.
This article is the weekend itself: what must be true beforehand, how the hours run, what makes it fail, and the honest cases where a weekend is not enough. The longer planning timeline is in the office move IT checklist.
What has to be finished before Friday
A weekend move is really a three-week move where the last two days are visible. Here is what I insist on having done before I unplug anything.
- Internet live at the new site, and proven. Not scheduled, not "the carrier says Thursday". I plug a laptop into the handoff and load a page. If the carrier has slipped, I want to know on Wednesday, when a temporary connection can still be arranged.
- Cabling terminated, tested and labeled. Every desk, printer and conference room has a jack that maps to a port on the patch panel. Details in data cabling and IT room setup.
- IT room staged. Rack mounted, patch panel connected, new or reused switch and firewall installed and configured, access points up. I configure the firewall and switch remotely during the week so that the room is a working network waiting for equipment.
- Full, verified backup of every server, NAS and workstation, stored off the truck. I restore a handful of files to prove it.
- Seating chart with drop numbers, and every device labeled to match.
- Phones sorted. Cloud phones just plug in. An on-premises phone system is a second server and needs its own row on the plan. Numbers being ported must have been submitted weeks earlier.
- Staff told the plan. When to shut down, that laptops go home, and that the new Wi-Fi password will be on their desk Monday.
If two or more of these are not done by the Wednesday before, I recommend moving the weekend rather than hoping. That call is cheaper on Wednesday than on Saturday afternoon.
Friday evening: shutdown and disconnect
Friday is the shortest day of the weekend and the one where care matters most, because this is when equipment gets handled.
- Late afternoon: staff save and shut down. I ask that everyone is out by a set time. Laptops leave with their owners. Anything on a desk that is not labeled gets labeled now.
- Servers and NAS shut down cleanly. Never pulled. I note which drive is in which bay, photograph the back of every device, and bag the cables per device with a label.
- Workstations unplugged and boxed or padded. Movers can carry these if the packing is right; original boxes or padded crates, monitors face-to-face with foam between.
- Network last. Firewall and switches come out at the end so the alarm, door access or cameras that ride on the office network are the last thing to go dark.
- Server and network gear travel with me, upright, in padding, in my vehicle or a dedicated crate that I load and unload. I do not hand a server to a general mover, and I recommend you do not either.
Friday evening is billed at after-hours rates, which are published on the pricing page. For a ten-to-twenty desk office with one server, the disconnect is usually an evening, not a night.
Saturday: reconnect in the right order
Saturday is the long day. The order matters because each layer depends on the one below it, and testing the top layer first wastes hours.
- Internet confirmed again at the handoff. Thirty seconds that saves a morning.
- Core equipment racked and up. Server, firewall, switch. The server boots, I check every drive is recognized and every service starts. This is the moment a truck-damaged drive shows itself, and the moment the Friday backup earns its keep.
- Printers and shared devices get their new addresses and I confirm they are reachable from the server.
- Workstations by drop number. Desk 7 to drop 7, per the seating chart. Each one is powered on, signed in, and checked for the shared drive and a printer.
- Phones registered, the main number rung from a mobile, a call transferred.
- Wi-Fi walked room by room with a laptop, guest network confirmed separate from staff.
- Backups started at the new site so that the first backup after the move completes before Monday.
I test from a user's chair, not from the rack. A network that looks perfect on the switch and cannot open the shared drive from reception is not finished. By Saturday evening the goal is a list of exceptions short enough to fit on one sticky note.
Sunday: the buffer, and why it must stay empty
Sunday exists so that Saturday can go wrong. If the plan needs Sunday to do scheduled work, the plan was too tight, and I say so at the walkthrough. When Saturday goes well, Sunday is a two-hour visit: fix the sticky-note items, walk every desk once more, and leave the Wi-Fi password and my number on each desk.
When Saturday does not go well, Sunday is where the move is saved. The common Sunday jobs are a workstation that will not join the domain, a printer that needs a driver, a line-of-business program that tied its license to the old server address and needs a vendor call on Monday, or a drop that tested fine and now does not. All of these are fixable in hours if there is a day to fix them in.
The one Sunday job that cannot wait for Monday is a server that will not come up. That is why the backup is verified on Wednesday and why I carry replacement drives for the server models I know. In the worst case, the restore runs Sunday onto replacement hardware and Monday still opens on time, slower than usual, with the story ending in a new server rather than a lost week.
What I ask of you on Sunday is simple: be reachable by phone, and do not schedule a Monday-morning client meeting in the conference room until I have confirmed the TV and the video system.
Monday morning: what I check before staff sit down
I am onsite early on the first Monday. Before the first person arrives, I have already walked the desks. Then I stay through the morning, because the things a weekend cannot test are the things real users find.
| Before staff arrive | Through the morning |
|---|---|
| Every workstation signs in | Individual saved passwords, mapped drives and printer defaults on each profile |
| Shared files open at normal speed | The one folder somebody had pinned that was on a different server |
| Email sends and receives | The scanner-to-email setting on the copier |
| Main phone number rings and transfers | Voicemail-to-email, call queues, the fax line if there is one |
| Wi-Fi in every room, guest separate | Personal phones and tablets joining, video meetings in the conference room |
| First backup at the new site completed | Line-of-business software re-activated where a license was tied to hardware |
For a law firm or dental practice, Monday also includes confirming the case management or practice management system, the imaging and the document scanners. I cover those specifics in moving a law firm and IT for dental practices.
What makes a weekend move fail
Every failed weekend move I have heard about, and the few near-misses I have had, come down to a short list.
- Internet not live. The single biggest cause. The carrier missed the date and nobody checked until Saturday. Prevention: prove it on Wednesday.
- Cabling scheduled for "the same weekend". Cabling is construction. It goes before the move, not during it.
- The server on the movers' truck. Handled like a filing cabinet, arrived with a failed drive, no tested backup. Prevention: it rides with me, and the backup is checked.
- No seating chart. Twenty computers, twenty desks, no labels. Saturday becomes a guessing game.
- Phone numbers not ported. Porting takes weeks and cannot be rushed on a Saturday.
- A building rule nobody asked about. Freight elevator bookings, after-hours access badges, a tower that requires its own low-voltage contractor. Ask the property manager at the first walkthrough.
- Scope creep on the weekend. "While you are here, can you also set up the new TV, the badge reader and the three new hires?" Yes, but on the following week, not between the server and the printers.
None of these need a bigger crew to prevent. They need someone who owns the whole list, has walked both spaces and has done it before. That is the argument for hiring an owner who is accountable for the move over a company that sends whoever is free on Saturday.
When a weekend is not enough
I would rather tell you at the walkthrough than on Sunday night. Here are the cases where I recommend a longer plan.
| Situation | What I recommend |
|---|---|
| More than about forty desks | Two weekends, moving departments in turn, or more of my team onsite on Saturday |
| Several servers, or a server that hosts a critical database | Move the server a week early or migrate it to the cloud first, then move desks on the weekend; see server room relocation |
| Internet not confirmed by the Wednesday before | Push the weekend, or arrange a temporary connection and accept slower speeds for a while |
| Cabling not finished | Push the weekend; there is no workaround for jacks that do not exist |
| On-premises phone system with number porting mid-flight | Keep the old system live at the old office until the port completes, forward calls in the meantime |
| Both offices in high-rise towers with freight elevator limits | Friday night for the IT room, Saturday for desks, and book both elevators in advance |
A weekend that stretches into a lost Monday costs more than a second weekend. When I quote a move as a project, the number reflects the plan that will actually work, not the one that sounds fastest.
Booking a weekend move with me
Weekend and evening work is billed at my after-hours rates, and I am available for it on any weekend of the year. The move itself is quoted as a fixed project price after I have walked both the old office and the new one, so you know the number before the first cable is unplugged. Cabling and internet at the new site are separate line items because they belong to the building.
What I need from you to book a date: the two addresses, the headcount, a floor plan or a sketch of the new space, whether you have a server, and the lease start date. From that I can tell you the same day whether your weekend is realistic and what has to happen in the weeks before it. A rough idea of the cost drivers is in how much it costs to move office IT.
If your office is in Dallas, Plano, Irving, Fort Worth or anywhere in the metroplex, send me the details and I will schedule the walkthroughs. You get one phone number for the plan, the weekend and the first Monday, and the same person answers it each time.
Questions people ask
Can a small office really move its IT in one weekend?
Yes, if the new site is ready. For an office of roughly five to forty desks with one server, disconnecting on Friday evening, reconnecting on Saturday and using Sunday as a buffer is the normal plan. The condition is that internet, cabling, the rack, switch, firewall and Wi-Fi at the new office are finished and tested before Friday, so the weekend is only for moving.
What has to be done before a weekend office move?
Internet live and proven at the new address, network cabling terminated and tested, the IT room racked and configured, a verified backup of every server and computer, a seating chart with drop numbers and matching labels on every device, and phones either cloud-based or planned separately. If two or more of those are not done by the Wednesday before, I recommend moving the date.
Who moves the server during a weekend move?
I do. The server, NAS, firewall and switches are shut down cleanly on Friday, photographed, bagged with their cables, and transported upright in padding in my own vehicle or a crate I load and unload myself. Desktops and monitors can go with the movers if they are packed properly. A server should not travel loose on a pallet with the furniture.
Does weekend IT work cost more?
Per hour, yes. Weekend and after-hours work is billed at my published after-hours rates. Overall, a weekend move is usually cheaper for the business because nobody sits idle on a weekday. For most small offices the cost of a lost business day is larger than the after-hours premium on the weekend work, which is why I recommend weekends by default.
What happens if something breaks over the weekend?
That is what Sunday is for. Common Saturday problems such as a workstation that will not sign in, a printer driver or a license tied to the old server are fixed in hours. A server that will not boot is the serious case, and the tested backup taken before the move is the answer: the restore runs Sunday onto replacement hardware so Monday still opens.
