The challenge
Carry the existing product into the next stage of development
The transition involved more than creating new screens. Member accounts and financial records had to fit the new application model, and authentication needed to accommodate credentials created by the earlier system.
The migration needed a defined process for transferring data and checking the result, alongside application behavior that respected existing accounts.
The work
Build the application around the new data model
We contributed to the Ruby on Rails architecture and the migration work needed to move established records into it. Historical implementation includes batch processing for transaction imports and explicit handling of legacy user data.
Preserve the existing password-verification path
The new application could evaluate passwords stored in the earlier format. Password-change handling then allowed accounts to move into the new credential format through normal account use.
Prepare the transition as an operational event
The migration work included pre-transfer validation and a planned cutover. The original Telos case recorded the completed transition and its scale.
What the work delivered
- A new application foundation built with Ruby on Rails.
- Migration tooling for established member and financial records.
- Compatibility with the earlier password format.
- Account-update behavior that supports transition to the new format.
The result
The platform transition preserved member sign-in continuity
Telos’s original SaverLife case reported more than 40 million records migrated and two hours of downtime. These figures describe the historical migration event and are retained here from the original case.
The application subsequently became the setting for additional program, engagement, and financial-guidance work described across this partnership.
