Server and Network Equipment Transport

Server hardware is not fragile in the way glass is fragile. It is heavy, dense, awkward in the hand, and expensive — and most of what goes wrong in transit happens while it is being handled rather than while it is being driven. That single fact shapes the whole approach: reduce the number of times the equipment is picked up, keep it identifiable end to end, and know before you start whether it is going into service, out of service, or out of the business.

How should server equipment be transported?

As a dedicated load. One vehicle, loaded once and unloaded once, with no depot leg and no consolidation with other customers' freight.

The reasoning is mechanical rather than sentimental: in a consolidated network a consignment is handled at every sortation point, and each handling event is an opportunity for impact, mis-stacking or misrouting. A dedicated movement removes almost all of them. It also removes the intermediate storage leg — the unrecorded overnight in a hub that nobody owns — which is exactly the gap that makes custody untraceable when the equipment holds data. The same driver stays with the load from collection through to delivery, so responsibility never transfers to somebody who did not see the equipment loaded.

What is the difference between moving equipment into service and out of it?

The paperwork and the destination, not the driving. Equipment going into service is goods; equipment being discarded is controlled waste, and the two travel under different rules.

The status follows the decision, not the condition — a working server sent for disposal is waste, and a broken one sent for repair is not. T&C Logistics holds Environment Agency registration CBDU654368 as an upper tier waste carrier, broker and dealer, so both directions run under one arrangement. Detail under end-of-life IT equipment.

How are data-bearing servers kept accounted for?

By an itemised handover against a list you prepare before anything moves, signed by both sides at collection. That fixes the moment custody transferred and to whom.

Whether the list is built at drive level or chassis level matters less than applying one of them consistently — mixing the two without recording which was used is what makes a large reconciliation impossible afterwards. Because the load stays dedicated, the assets that leave the building are the assets that arrive, which is what later allows an erasure or destruction certificate to be checked against reality rather than taken on trust. See chain-of-custody IT collection.

What preparation makes a server move go smoothly?

Five steps, all of which are quicker before the vehicle arrives than after it.

1. Decide the destination category — redeploy, store, repair or dispose. It determines the paperwork.
2. List the equipment by serial number, flagging anything data-bearing.
3. Identify batteries, since certain types are classified as dangerous for carriage under ADR.
4. Stage the equipment somewhere a vehicle can reach without a lift journey per item.
5. Declare the consignment value so cover above the standard limit is arranged rather than assumed.

Should equipment travel in its original packaging?

Where it still exists, yes. Original manufacturer packaging is designed around the specific device and its mounting points, and nothing improvised matches it.

In practice it rarely survives past installation, so most server moves are of unboxed equipment — which is another argument for a dedicated load, since unboxed hardware tolerates far fewer handling events than boxed hardware does. Equipment should travel upright where it was designed to sit upright, restrained against movement, and not stacked under anything heavier than itself. Rather than improvising protective materials, the more effective control is reducing the number of times the equipment is touched between the two racks. On a dedicated movement that count is two — once at the collection rack and once at the destination — whereas a consolidated network handles the same consignment at every sortation point on the route, and each of those is an event that improvised wrapping is being asked to survive.

What if the equipment is leased or still under warranty?

Separate it from owned equipment before the move, because the two have different destinations and different consequences if they are confused.

Leased hardware normally has to be returned rather than redeployed or disposed of, and a leased unit that goes for treatment by mistake is both a contractual problem and an untraceable one. Warranty terms can also specify how equipment is transported or who may open it, which is worth checking before a chassis is stripped. The practical rule is the same as for the disposal question: decide the fate of each asset once, at the point it comes out of service, and record it on the list.

How is a multi-site server move sequenced?

Site by site, with documentation per movement rather than per project. The paperwork follows the location, so a programme across several buildings is a set of separate movements running to one plan.

1. Survey each site — access constraints do not generalise between buildings.
2. Fix the order by service dependency, not by convenience.
3. List per site, so each consignment reconciles on its own.
4. Book windows per site, since each has its own access regime.
5. Close out each movement as it happens, rather than at the end of the programme when the detail has been lost.

Does network hardware need different handling from servers?

Not in transit, but it behaves differently in the load. Switches, routers and patch panels are light relative to their volume, whereas storage arrays are the opposite.

The practical consequence is that vehicle requirement is driven by cabling and network gear far more often than by the servers themselves — bulk structured cabling pulled from a suite consistently exceeds estimates and fills space without adding weight. Planning by weight alone is what leads to a second vehicle being needed on the day. Where a full suite is coming out, see data centre decommissioning.

What drives the cost of a server move?

Access, timing and declared value rather than weight. We quote one fixed price per job upfront, with fuel and goods-in-transit cover included and no hidden charges.

Can you collect from a colocation provider?

Yes, though the provider's access rules govern the visit rather than ours. Colocation sites run their own security, escorting and booking regimes, and those set the timetable.

The practical requirements are usually the same everywhere: the collection has to be pre-authorised with the provider, the attending driver's details registered in advance, and the equipment identified precisely enough that it can be released from a shared suite without ambiguity. Whereas an office collection can be arranged on short notice, a colocation collection is gated on the provider's own lead time. Rack-level constraints are covered under server racks, and facility-level ones under data centre equipment.

What insurance applies to a server consignment?

Goods-in-transit cover of £50,000 on our own vehicles, extendable to £1,000,000 through our partner network where the consignment value requires it.

The number that matters is the declared value, not the pallet count — a single populated storage array can exceed the standard limit, and cover is arranged against what is declared rather than against what is assumed. Confirming it at booking costs a sentence and is the difference between a claim that pays and one that argues. Detail under goods-in-transit insurance.

What records do you get after a server move?

What the movement produces depends on what it was. A relocation generates a delivery record; a disposal generates a waste transfer document and a named treatment destination.

Where the consignment was itemised, the handover record lists what transferred rather than how many units moved, which is the part that later makes an erasure or destruction certificate checkable. Vehicles are GPS-tracked throughout, so the movement itself is evidenced independently of anyone's recollection. For disposals the full document set — transfer note, asset list, destruction evidence, treatment destination — is set out under IT disposal documentation, and the transfer document itself under waste transfer note.

Where and when can server equipment be collected?

Nationwide, 24/7, through a network of more than 3,000 vetted driver-partners. Vehicles run under our Operator's Licence and are GPS-tracked throughout.

Out-of-hours attendance is normal for this work rather than exceptional, because server moves are usually scheduled around service windows rather than office hours. ADR-licensed drivers cover loads containing items classified as dangerous for carriage, which most often means batteries. Related pages: server racks, data centre equipment and emergency IT replacement. To arrange a collection, get in touch or call +44 7963 400173.