Frequently asked questions about data center exits

Discovery and reporting usually take longer than the physical work. Building access and data requirements set the pace, not rack count.

A physical inventory, a dependency map and a data classification. The checklist covers the rest.

Yes, where access allows. What should stay identical across sites is the reporting standard, not the schedule. See enterprise programs.

Erasure keeps resale value and needs per-serial verification. Destruction is unambiguous and forfeits recovery. See the comparison.

Only if your own obligations require it. Off-site is cheaper and faster but adds a transport leg during which the data still exists.

Serial numbers rather than counts, the method per device, custody dates, the facility, and the exceptions. That last item is the one most often missing.

Sometimes, with recent homogeneous complete hardware sold at decommissioning rather than months later. A possible outcome, not a plan.

Access, data requirements and how recovery value is treated. The six factors explain most of the gap.

Often the same party that buys them. Not necessarily a problem, but a structural conflict worth naming, or separating.

A qualified decommissioning and ITAD provider covering your sites, under its own contract and certifications. We call you back to scope the project, then, with your agreement, pass the scoped request to that provider, who should name every subcontracted stage before you sign. See how a request works.

No. Submitting a project and the call back that follows cost nothing. The site is paid by the provider that receives the scoped request, not by you.

No. It is used for your project only, and shared only with your agreement and only with the one provider who quotes the work. See the privacy policy.