Can This Building Be Converted Into a Data Center?

When a council member publicly raises concerns about a property becoming a data center, it signals an important shift: the conversation around data infrastructure has officially moved out of the server room and into city hall. The question of whether a building *can* be converted is almost always simpler than whether a community will allow it.

That tension—between technical feasibility and local acceptance—is exactly where most data center conversion projects succeed or fail. Understanding both sides isn't optional anymore; it's the whole job.

What a Data Center Conversion Actually Involves

A data center is, at its core, a facility purpose-built (or purpose-retrofitted) to house computing equipment—servers, networking hardware, storage systems—that process and transmit data. The demand driving these projects is not abstract. Global data creation is growing at a rate that existing infrastructure simply cannot absorb. Hyperscalers like Amazon Web Services, Microsoft Azure, and Google Cloud are in a continuous land-and-building grab. So are the colocation providers serving mid-market enterprise clients.

The result is that developers and investors are looking at underutilized buildings—old warehouses, shuttered big-box retail, former manufacturing plants—and asking a legitimate question: could this work?

Sometimes the answer is yes. Sometimes it's a costly no that only reveals itself after significant due diligence. The difference comes down to a handful of hard factors.

The Feasibility Questions That Actually Matter

Structural Load Capacity

Standard commercial or industrial buildings are not designed to hold what a modern data center demands. Server racks are dense and heavy—floor load requirements for a data center typically range from 150 to 250 pounds per square foot, compared to roughly 50–80 pounds per square foot in a typical office building. Reinforcing an existing structure to meet those specs is possible, but the cost can be substantial enough to undermine the project's economics entirely.

Before any conversion moves forward, a structural engineering assessment isn't a formality; it's the first gate.

Power Infrastructure

This is where most conversions either get exciting or fall apart. A mid-sized data center might draw 10 to 30 megawatts of power—and large hyperscale facilities push well beyond 100 MW. The existing electrical infrastructure serving the building, and the utility grid serving the surrounding area, has to be able to support that load or be upgraded to do so. Grid connection timelines in many U.S. markets are now running three to seven years for large interconnection requests. That's not a footnote; it's a project timeline.

The building you're evaluating may be perfect in every other respect, but if the utility substation nearby is already constrained, you're looking at a multi-year infrastructure investment before a single server goes live.

Cooling — the Hidden Complexity

Servers generate massive amounts of heat. Removing that heat efficiently is one of the central engineering challenges of data center design. Legacy buildings rarely have the mechanical infrastructure—raised flooring, adequate ceiling height, chiller capacity—to support modern cooling systems without significant modification. Air-side economization, liquid cooling, and immersion cooling are increasingly common, but each requires specific building conditions to implement effectively.

Location, Access, and Connectivity

Proximity to fiber networks matters. Proximity to major roads for equipment delivery matters. Distance from flood zones, flight paths, and other risk factors matters. A building that looks attractive on paper may sit in a location that makes it functionally unsuitable for data center use—or that triggers land use planning conflicts that slow the project by years.

When the Community Pushes Back

Council member Devon Reese's concern reflects a pattern playing out in municipalities across the country. Data centers carry a mixed reputation at the local level, and not without reason.

On one hand, they represent significant capital investment and generate substantial property tax revenue. On the other, they employ relatively few people compared to the square footage they occupy, consume enormous amounts of power and water, and can alter the character of a neighborhood without providing much visible community benefit.

The communities that navigate this friction best treat data center developers like any other major infrastructure project: requiring transparent community engagement, clear impact assessments, and negotiated community benefit agreements before approvals move forward.

Local perceptions are often shaped by incomplete information. Residents may not understand that a modern, well-designed data center is far less disruptive than a traditional industrial facility. The noise, the truck traffic, the utility strain—these are manageable with proper planning, but someone has to do the work of explaining that. When developers skip public engagement or treat it as a box-checking exercise, opposition hardens fast.

The insider reality is that experienced data center developers now budget for community relations the same way they budget for civil engineering. It's a line item, not an afterthought. Companies that underestimate this spend more time fighting zoning battles than building infrastructure.

The Economic Case — and Its Limits

The economic argument for data center conversions is real, but it requires some intellectual honesty.

On the positive side: a large data center project might represent $500 million to over $1 billion in capital investment for a single campus. Property tax revenues from that assessed value can be transformative for smaller municipalities. Construction phases generate substantial local employment—electricians, engineers, general contractors, equipment installers. And once operational, data centers create stable, well-paying jobs in facilities management, security, and network operations.

The honest caveat is that direct employment numbers are modest for the facility size. A 100,000-square-foot data center might employ 30 to 50 full-time staff. That's meaningful, but it's not a manufacturing plant bringing 500 jobs to a region. Local elected officials need to weigh that reality against the infrastructure investment and tax base expansion—and they increasingly do.

Some jurisdictions have learned to negotiate aggressively: requiring local hiring provisions, green energy commitments, or community investment funds as conditions of approval. That's not obstruction; that's infrastructure development done correctly.

Technical Conversions: What Has to Change

Assuming the structural and power fundamentals check out, the technical conversion of a building into a functioning data center is a significant construction undertaking. Key modifications typically include:

• Electrical upgrades: Installing high-capacity switchgear, backup generators, and uninterruptible power supply (UPS) systems. Redundancy is not optional—brief power interruptions can cause data loss and service outages worth millions of dollars.
• Cooling systems: Installing precision air conditioning units (CRACs or CRAHs), chillers, and cooling towers, or designing for newer liquid cooling approaches.
• Security infrastructure: Data centers require layered physical security—perimeter fencing, access control systems, CCTV, mantrap entries. Many hyperscale tenants require SOC 2 compliance as a baseline.
• Fire suppression: Standard sprinkler systems are inadequate for server environments. Clean agent suppression systems (typically FM-200 or similar) protect equipment from water damage while controlling fire.
• Raised flooring or overhead cabling: Cable management at scale is a genuine design challenge. Most modern facilities choose one approach and commit to it from the start.

None of this is insurmountable. But the cumulative cost of these modifications can easily reach $10 to $20 million per megawatt of IT load for a purpose-converted facility—sometimes more, depending on existing conditions. That's why the building feasibility assessment has to be rigorous and honest before capital commitments are made.

What Comes Next

The buildings best positioned for data center conversion aren't necessarily the most impressive. They're the ones sitting near robust power infrastructure, on fiber-rich corridors, in jurisdictions with pragmatic zoning frameworks—and with owners and developers willing to do the community engagement work that transforms a controversial project into a welcomed one.

Council member Reese's concern isn't a roadblock; it's an invitation to have a better conversation. The projects that treat local governance as a partner rather than an obstacle tend to move faster, face less litigation, and ultimately build something the community can live with—sometimes literally.

If you're evaluating a building for conversion potential, the technical questions have answers. The community questions require a different kind of preparation. Start both conversations early and run them in parallel.

Ready to explore data center conversion opportunities? Visit our marketplace for more insights: [InfraSale Marketplace](https://infrasale.com/marketplace).

[INTERNAL LINK: data center conversion process]

[INTERNAL LINK: community engagement strategies]

[INTERNAL LINK: economic impact of data centers]