Nick Herrera

IT asset logistics from receiving dock to ITAD, and who owns each handoff.

The fields an IT asset inventory needs, with an example value for each.

Anti-static packing done right: which bag, which foam, and what needs neither.

When servers need climate controlled transportation, and what to ask for.

GPU server transportation: weight, shock, value, and how to ship them safely.

MDF vs IDF: the main telecom room, the floor closets, and the cable between.

What a server removal company does and the paperwork you should get back.

Data center relocation equipment, from rack dollies to air-ride trucks.

Most IT shipments need an unarmed escort. Some need armed security escorts.

Secure tech transport is a set of controls, not a word on a quote.

Disaster recovery warehousing is about distance, access, and release time.

Reopening forty stores after a storm is a hardware logistics problem.

The office move ends when the network works, not when the desks arrive.

Cold servers in a warm room collect water before they collect uptime.

A rack that is not anchored becomes the hazard in an earthquake.

A move of two hundred feet still needs a work order, a route and a new circuit.

Cargo theft needs an unattended trailer or the wrong driver at the dock.

Moving the servers out is half the exit. The lease decides the other half.

A crew with the wrong certificate does not get past the loading dock.

The regulations that govern the truck decide when your equipment arrives.

Forty small sites with no IT staff fail differently than one big data center.

A replacement server does no good parked behind a roadblock.

A server room below the flood line is a recovery plan waiting to be used.

Hardware that leaves before the roads close is hardware you still own.

A lessons-learned document nobody acts on is just a list of excuses.

Rollback is easy on paper and hard once the servers are on a truck.

A planned outage nobody was told about is an unplanned outage.

Most move-day failures were decided ninety days earlier.

A generator's runtime is set by the fuel you can actually get, not the tank.

After ransomware, the servers you have may be evidence, not recovery targets.

Once a storm has a name, the time to prepare has mostly passed.

A four-hour RTO that needs new hardware is a promise nobody has priced.

Criminal justice data does not get a relaxed standard because it is on a truck.

The lessor wants the hardware back. Your data should stay behind.

Your auditor will ask about the move. Collect the answers during it.

A custody form is only as good as its weakest handoff.

Shut down from the top of the stack. Bring it back from the bottom.

A risk nobody wrote down has no owner when it happens.

The firm that wins the bid is not always the firm that shows up.

The truck is the short part. The months before it decide the date.

Standard freight delivers to a dock. Everything after that is scope.

Migrating a storage estate without first measuring it moves the problem.

A GPU rack can draw more than an entire row of conventional servers.

Edge sites fail on power, access, and temperature long before hardware.

A seal does not prevent access. It proves access happened.

The right sanitization method depends on the media, not the policy.

A certificate that cannot name serial numbers proves almost nothing.

Running hardware past warranty is a decision, even when nobody makes it.

The three-year refresh is an accounting convention, not an engineering one.

Liability for a retired drive does not transfer with the truck.

Discovery tools find what is powered on. They miss what matters most.

An asset tag that falls off in transit takes the audit trail with it.

The freight quote is the smallest line item in a relocation budget.

Hardware arrives at the new site. Its support coverage often does not.

Most transit damage happens to equipment that was packed by hand, badly.

A recovery plan that assumes replacement hardware is available is a guess.

What survives a flood or a fire depends mostly on the first 48 hours.

A four-hour SLA means nothing if the part is three weeks from your site.

Cooling equipment leaves a facility under environmental law, not IT policy.

Every person on the floor is an access decision someone has to own.

Batteries are regulated dangerous goods, and the rules differ by chemistry.

The route from the truck to the rack position is where moves get stuck.

Liquid cooling turns a rack move into a plumbing project.

The rack fits the space. The question is whether the floor holds it.

Security certifications describe the freight controls buyers keep asking for.

Liability for improperly disposed equipment follows you, not the hauler.

Loose media is the highest-risk, lowest-visibility part of any equipment move.

A runbook written once describes an environment that no longer exists.

A DR site is a production build with a harder problem: keeping it current.

Vague scope produces bids you cannot compare and change orders you cannot refuse

One authoritative record, or six spreadsheets that disagree with each other.

How to plan a storage array move: shutdown order, drives, weight, fabric.

Deracking is the easy part. Everything that makes it safe happens earlier.

The approach is chosen by outage tolerance and budget, not by preference.

Consolidation is many migrations sharing one destination and one deadline.

A loaded chassis is a quarter ton in four rack units. Weight drives the plan.

Destroying data under hold is a problem no certificate will resolve.

Cleared personnel and classified spaces change who can touch the equipment.

Declaring a disaster is a decision. Executing one is a logistics problem.

HCI ties compute and storage to the same nodes. Move order is not cosmetic.

Coverage is easy. Capacity, roaming, and interference are the hard parts.

The cable plant is poured concrete. You get one chance to do it right.

The provider inherits your site access, hardware, and compliance duties.

Carrier liability is set by weight. Your equipment is not priced by weight.

Distance buys independence and costs latency. Both are measurable.

Prefabricated capacity trades cost for speed. The tradeoff is site readiness.

Telecom rooms carry the carrier demarc. They set the schedule, not the servers.

Fiber fails quietly. The damage shows up as degraded links, not dead ones.

How to receive, rack and cable a new facility without losing the schedule.

What changes when IT equipment and data cross a national border.

Powering on is not the same as working. What to test before releasing.

How your IT team maps application dependencies and turns them into move groups.

How hot, warm and cold standby sites compare on recovery time, cost and upkeep.

Standing up interim capacity when origin and destination must both run.

What auditors ask for after a migration, and how to capture it during one.

Recovery time is usually consumed by sourcing and shipping, not engineering.

How decisions, communication, and escalation actually work during execution.

Labeling and port mapping practices that hold up when everything is unplugged.

Why mainframe moves follow different rules than the rest of the floor.

Moving storage networks while keeping every host on at least one working path.

How to move a tape library and its media without damaging robotics or tapes.

When an IT shipment needs a security escort, what it provides, how it's logged.

Why most DR tests pass and most DR events fail, and how to close that gap.

The site survey is where migration risk is found or missed entirely.

How to plan the physical side of bringing workloads back from public cloud.

How to move GPU and AI clusters: weight, power, liquid cooling and bring-up.

Parallel, rolling and blue-green migrations, and who does which part.

What HIPAA, PCI DSS, SOX, GDPR, FedRAMP and ITAR add to a data center move.

Power and cooling best practices for data center relocations.

The five phases of the IT asset lifecycle and what each one should record.

Distance, hazards, power, carriers and access: how to pick a DR site location.

How IT teams plan storage migrations, and where the physical array move fits.

A five-phase plan for replacing switches, routers and cabling without outages.

How to decide whether an aging server should be retired or redeployed.

How to keep an unbroken custody record for every asset in a data center move.

Navigate the logistics of combining two IT environments after M&A.

How to keep IT asset records accurate from the receiving dock to disposition.

Complete process for safely decommissioning a data center facility.

Master the logistics challenges of deploying edge computing infrastructure.

How to retire IT assets securely and sustainably: destruction, reuse, recycling.

How SOX and PCI DSS shape moving, storing and retiring financial IT equipment.

How to document every handoff when data-bearing IT equipment leaves your site.

How to plan a colocation migration: facility choice, timeline, move day, checks.

Navigate HIPAA compliance for healthcare IT equipment logistics.

When to refresh enterprise servers and how to plan the swap and retirement.

How to relocate switches, routers and cabling while keeping the network up.

Plan your disaster recovery site with the right hardware and logistics.

NIST SP 800-88 explained: Clear, Purge and Destroy, by media type.

How a data center relocation works: survey, strategy, transport and validation.