Resource Innovations Used Files.com to Retire Its FTP Server and Rebrand Without Partner Reconfiguration

Resource Innovations is an energy transformation firm that designs and runs energy-efficiency, demand-side management, and clean-energy programs on behalf of utilities. It serves more than 200 clients across North America, Europe, and the Pacific, delivers programs in over 30 states and 10 countries, and in 2024 alone put more than $710 million in rebates into customers' hands. Before 2021, this work ran under the name Nexant, which combined with Resource Innovations that year.

The business model is intermediation. A utility hires Resource Innovations to run a program that touches the utility's own customers, so program data moves between the two organizations constantly: enrollment files, incentive and rebate records, measurement and evaluation data. Every client engagement comes with a file exchange attached. And for years, all of those exchanges converged on one machine the company hosted and operated itself. Files.com ultimately let Resource Innovations change both the platform behind that exchange and the company name in front of it without requiring utility partners to reconfigure scheduled jobs.

A Server the Entire Delivery Model Pointed At

The on-premise FTP server was the exchange point between the company's staff and the utility clients and partners whose programs it implements. Counterparties reached it at a hostname, through desktop FTP and SFTP clients and scheduled jobs running on their own side of the exchange.

That arrangement carried a cost the company felt every time it wanted to change anything. It owned, patched, and operated transfer infrastructure that its entire client-delivery model depended on, and it could barely touch that infrastructure, because every external counterparty's automation was pointed at it.

Replacing a transfer server is not hard because of the server. It is hard because of everyone connected to it. Resource Innovations could not tell its utility clients to update scheduled jobs, reconfigure transfer clients, or redo key exchanges on its own timetable. Any cutover that required simultaneous action by organizations it does not control was a cutover that would break some of them. So the server stayed, and the dependency on it deepened with every new client connection.

The Replacement Had to Absorb the Old Address

The requirements for a replacement follow directly from that constraint. It had to speak FTP and SFTP, so the software counterparties already ran would connect unchanged. It had to serve web users and protocol users from the same folders, because internal analysts and external scheduled jobs work against the same data. It had to run under the company's own name rather than a vendor's. And decisively, it had to answer on the legacy hostname the old server had answered on, so that a partner job pointed at the old address would keep working after the server behind that address was gone.

Put plainly: the address had to move to the new platform, instead of every counterparty moving to a new address.

Resource Innovations selected Files.com to be that endpoint.

New Estate First, Server Retirement Second

The rollout began under the Nexant name and ran through 2017 and 2018. The site launched on a branded subdomain of the company's own domain, with a custom-styled welcome page, so nothing about the exchange looked like a third-party tool. A parallel testing phase set the organizational standards before the platform opened to an active population of 350 to 400 SFTP users. Because Files.com serves the web portal and the protocols from the same folders, a utility team on a desktop transfer client and an internal analyst in a browser reached the same files under the same permissions.

The old server kept running while the new estate took over the work. Then, in 2019, came the step the whole approach was built for: the company decommissioned the on-premise FTP server and pointed its legacy hostname at the Files.com site. Files.com carried both names at once. The new branded address and the retired server's old address resolved to the same platform, so a counterparty whose scheduled job still targeted the old hostname never had to know the server was gone.

“We finally decommissioned our old on-premise FTP server.”

"Finally" is the word doing the work in that sentence. The retirement had waited not on technology but on a way to do it without asking anything of the organizations connected to it.

A Corporate Rebrand in a Fifteen-Minute Window

In 2021 Nexant combined with Resource Innovations, and the branded exchange domain had to follow the new company name. This was the same problem in a larger form: clients' existing scheduled jobs were pointed at the current URL, and changing it risked breaking them.

Because the endpoint was Files.com rather than a server, the change was a planned maintenance window rather than a migration. DNS time-to-live was lowered to 60 seconds a few days ahead, the certificate for the new domain was put in place, and then the DNS record and the Files.com domain setting were changed together in a scheduled overnight window, with 5 to 15 minutes of expected downtime. The company renamed the front door of its entire client file exchange without a single counterparty reconfiguring a job.

What Retiring the Server Bought

With the exchange on Files.com, Resource Innovations replaced a server it had to operate, and could never safely change, with an endpoint whose address it controls.

• The on-premise FTP server is gone, with no forced counterparty migration. Existing scheduled jobs and client software ran uninterrupted through the cutover, and there is no box left to patch, size, or defend.
• Onboarding a new utility client or partner is a routine request. The team shares the site details and exchanges keys, and the counterparty connects with whatever client they already run.
• The exchange has grown without new infrastructure behind it: 25 outbound and AS2 connections, five on-premise Files.com Agents reaching internal systems, and roughly 20 TB of data moving a year.
• When a prospective client ran a security control review, the platform's security documentation answered it. That is evidence the company can hand over, rather than a self-hosted server posture it has to defend on its own.

An Exchange Point That Outlived Its Server and Its Name

The address of the company's file exchange is now configuration, not infrastructure. Today the file exchange between Resource Innovations and the utilities it serves runs on Files.com, under the company's own name, reachable by web portal and by the protocols its partners' automation already speaks. Before, any change to the endpoint meant asking organizations the company does not control to change with it, so nothing changed. Since moving to Files.com, the company has swapped out the platform behind the address and then the address itself, through a server retirement and a full corporate rebrand, and no utility partner had to touch a scheduled job or reinstall a client for either one.

That is the lesson a team still running its own transfer server can take from this story: retiring the server does not require a coordinated migration across every counterparty pointed at it. Carry its hostname onto the new platform, and the partners never have to move at all.