BlueScope Buildings Took Custody of 50,000 Candidate Records on Files.com Before Retiring Click Boarding

BlueScope Buildings North America designs and manufactures engineered low-rise building systems across seven manufacturing facilities with more than 2,000 employees. An operation that size hires continuously, and its hiring runs through software.

For years, candidate onboarding and applicant tracking ran through Click Boarding. The records that accumulate in a system like that carry legal weight: they are what HR reaches for when an auditor asks a question or a discrimination claim needs a defense, and the obligation to produce them runs for years. It outlasts the system that collected them.

Hiring Moved to Workday, but the Records Had Nowhere to Go

In late 2024, BlueScope moved hiring to Workday and prepared to retire Click Boarding. That created a problem the two systems could not solve between themselves: there was no direct export from Click Boarding into Workday. Workday would take over hiring going forward, but it was never going to absorb the archive. HR planned to import only selected candidates’ histories, and everything else still had to exist somewhere BlueScope controlled.

Everything at stake was in Click Boarding’s hands: an estimated 50,000 to 60,000 candidate records, each an individually zipped set of a candidate’s forms. Once Click Boarding was retired, whatever had not been extracted would be out of reach. Without the archive, HR could not answer an audit request or defend a discrimination claim from its own records, and it would lose the source data it needed to bring candidates forward into the new system.

An Export Dictated Entirely by the Departing Vendor

What made the exit hard was that BlueScope controlled none of the mechanics. Click Boarding delivered the export its own way: one-way pushes over its API into a designated location, with no browse access on BlueScope’s side. There was no directory to inspect, no way to pace the delivery, and no way to restructure it in flight. Click Boarding sent what it sent, and BlueScope received what arrived.

The shape of the data compounded it. Tens of thousands of small zip files, with the number of documents inside each varying wildly per candidate, is far past what anyone files by hand. Landed unsorted in a single folder, the set would be an archive in name only, unusable for the years of HR lookups ahead. And the extraction had to be verified while Click Boarding was still available, because once it was retired there was no re-running it.

So the destination had to do four things: accept a bulk API push on the vendor’s terms, organize tens of thousands of files as they arrived, keep them retrievable for HR years later, and hold them under BlueScope’s own governance. BlueScope made Files.com that destination: the receiving point for the export and the permanent home for the archive.

A Test Export First, Then Records That Sorted Themselves on Arrival

BlueScope’s system administrator, working with Files.com onboarding support, set up a designated Files.com location for Click Boarding to push into. Before anything ran at volume, a small test export was delivered and checked to confirm that the format and contents matched expectations. Only then did the production export run.

Each record arrived as a zip named for the candidate it held. A Files.com Automation, driven by a regular expression against those filenames, moved every file into the alphabetical subfolder matching the candidate’s surname the moment it landed. The archive organized itself as it arrived. No one touched a file by hand, and the first place BlueScope could actually see and browse its own candidate records was on Files.com.

The Click Boarding Exit Left the Compliance Record Intact

With the production export complete, BlueScope retired Click Boarding holding its own compliance record instead of relying on continued access to the vendor’s application.

• The entire export, an estimated 50,000 to 60,000 candidate records, landed on Files.com organized and browsable, with nothing filed manually.
• HR answers audit requests and defends discrimination claims from records BlueScope holds and governs itself, with no dependence on a vendor it no longer uses.
• When a candidate’s history is needed in the new system, HR pulls the record from the Files.com archive and imports it into Workday: the export path the two HR systems never had between them.

Absorbing the departing vendor’s entire data set took configuration, not a custom development project.

Records That Outlive the Systems That Produced Them

Click Boarding is gone, Workday runs hiring, and the candidate records answer to neither.

What BlueScope’s exit shows is that leaving a SaaS vendor is less a migration problem than a custody problem. The records did not need a successor system capable of importing all of them. They needed a home that does not depend on any application at all, and Files.com became that home.