IT Projects & Migrations
Moving office, replacing a server, changing IT providers or shifting to the cloud: the projects that go badly are the ones nobody planned properly. GravIT runs these as actual projects: discovery first, a design you sign off, a rehearsal, then a cutover outside business hours, with someone on site the morning after.
Projects fail at the ordering, not the engineering
Almost nobody's office move goes wrong because a network was configured badly. It goes wrong because something was ordered six weeks too late, and no amount of technical skill on the day compensates for a service that has not been installed yet.
Roughly how far ahead things need to start, longest first:
- nbn Enterprise Ethernet40–60 business days. It is a build rather than a connection, so if you need it, it is the first phone call of the whole project.
- Cabling and electricalTrades have their own calendars, and a fitout has several trades who all want the same week.
- Business internet at a new addressWeeks, and entirely address-dependent. The answer at your current site tells you nothing about the new one.
- Porting phone numbersSet by your current provider, not by us. We lodge it and chase it, and confirm the window once they give one.
- Hardware with anything unusual in itOrdinary gear is quick. The one part with a long queue is what holds the whole order, and stock is not a plan.
- Licences and accountsFast, which is precisely why it is never the thing that causes the problem.
Read that from the bottom up and you have the usual failure: the quick things get organised first because they are easy to organise, and the long ones get noticed once a date is already locked in. Discovery exists to find the top of that list on day one, which is why we do it before quoting rather than after winning the job.
The projects we get called for
- Office moves and fitouts. Cabling, network, internet ordered early enough to actually arrive, and everything working on day one.
- Server replacement. Or retiring the server entirely into private cloud hosting.
- Cloud migrations. Email, files and applications moved without losing anything.
- Changing IT providers. Taking over from someone else, cleanly.
- New sites. A second location that works like the first one.
How we run them
- Discovery and assessment. A full inventory of what you have, what depends on what, and what will bite us.
- Design you approve. Right-sized, costed, and agreed before anything is bought or built.
- Rehearsal. We test the migration before the real one, so cutover night holds no surprises.
- After-hours cutover. Done when your business is closed, with a rollback path if it is needed.
- Go-live support. We are there the next morning, when the questions actually arrive.
What's included
- Discovery and inventory
- Costed design, signed off first
- Rehearsal migration
- After-hours cutover
- Go-live support and handover
Frequently asked questions
Can you take over from our current IT provider?
Yes, and we do it regularly. Transitions are handled deliberately: documentation gathered, access transferred, nothing switched off until the replacement is proven.
Do we need to be a managed client first?
No. Plenty of clients meet us through a project, and that is often how it should start, because you get to watch us work before committing to anything. We will say plainly that we prefer ongoing support contracts, because a project we hand over and never see again is a project we cannot stand behind for long. But we are not going to refuse the work to make a point.
How do you avoid the classic office-move disaster?
By treating the internet connection as the long-lead item it is, ordering it early, and testing everything before move day rather than on it. Most office-move IT failures are ordering failures, not technical ones.
What does a project cost?
Quoted per project after discovery, so you get a real number rather than a range that moves.
What happens if something goes wrong on cutover?
There is a rollback path agreed before we start, and we rehearse first. That is the whole reason for the rehearsal.
IT projects planned before they get urgent
Office move, server replacement or a provider you have had enough of: let's scope it properly.