For financial services companies, growing demand can be hard to meet with physical servers alone. Adding capacity takes time, and customers still expect to be able to use online services around the clock. Cloud infrastructure makes it easier to scale as demand changes. A cloud migration also has to keep the systems customers already use available during the move.

That was the challenge for TakTo, a Polish online lender. Spyrosoft moved TakTo’s existing workloads to Amazon Web Services (AWS) in stages and finished three weeks ahead of schedule. Customers and staff experienced no service disruption. After the AWS migration, TakTo could launch virtual machines within minutes and switch off idle environments.

If you’re planning a similar move, this case study shows how Spyrosoft tested the AWS infrastructure and transferred core databases while keeping TakTo’s online services available.

Barriers to cloud adoption in financial services

For years, financial institutions ran on mainframes, large in-house applications, and paper-based processes. Moving these systems to a public cloud platform raised questions about data security and service reliability. Customers expected to make payments and access their accounts securely, and they wanted transactions to go through without delay.

Regulatory uncertainty also slowed adoption. In the EU and the US, some institutions saw financial regulations as a barrier to using cloud services. With limited guidance on how existing rules applied to cloud outsourcing, some firms postponed modernisation.

How regulation changed the picture for cloud in finance

The turning point came in 2016, especially in Europe. In the UK, the Financial Conduct Authority published guidance on cloud services stating that cloud can be used in financial services as long as data hosting and security are appropriately considered. Statements from the Information Commissioner’s Office and the Bank of England’s Prudential Regulation Authority supported the shift.

Regulators and industry professionals also recognised that cloud was already used in other sectors handling sensitive data. Since then, European rules have continued to evolve: the EBA’s guidelines on outsourcing arrangements and, most recently, the Digital Operational Resilience Act (DORA), applicable since January 2025, set clear expectations for how financial entities manage ICT and cloud providers’ risk.

Once the rules were clearer, technical solutions followed. AWS became one of the platforms widely used to build secure financial IT infrastructure.

Matching cloud capabilities to business requirements

A customer-facing application and an internal test environment have different needs. The first may need to run around the clock, while the second may only be used for a few days before a release. Understanding how teams and customers use each workload helps determine what computing capacity and storage to provision.

Security and compliance also shape the migration strategy for firms subject to strict regulatory requirements. Teams need to understand who can access sensitive data, how to protect it during the data transfer, and how to recover critical workloads if a service fails. Those questions help determine which systems to migrate first.

Why TakTo chose AWS

TakTo is an online lender based in Wrocław, Poland. Founded in 2012, the company lets customers apply for loans through online chat and manage repayments through a dedicated platform. TakTo follows the principles of ethical conduct and the Best Practices Guide issued by the Association of Financial Companies in Poland (ZPF).

For years, TakTo ran its application on physical servers at a facility outside its headquarters. The hardware needed on-site technical support and a controlled environment. As the business grew, it became harder to manage capacity without investing in more equipment.

Spyrosoft assessed TakTo’s business requirements and designed AWS infrastructure around the existing application. Keeping the lending and repayment platform available throughout the move was a core requirement.

How AWS cloud services can help companies in fintech

Reliability

Teams can deploy workloads across multiple AWS Availability Zones to reduce the risk that a failure in one location interrupts the whole application. The level of resilience depends on how the system is designed and how the team tests recovery.

Scalability

Virtual machines give teams a way to add computing capacity as demand grows. After moving to AWS, TakTo could launch additional servers within minutes. For workloads with predictable scaling rules, teams can also automate when capacity is added or removed.

Security

Teams can use scripts to set up cloud infrastructure consistently and track configuration changes alongside software releases. Backups and disaster recovery procedures help teams prepare for failures. For TakTo, the immediate priority was to back up the core databases before the final data transfer so Spyrosoft could restore them if needed.

Flexibility and cost control

AWS offers pay-as-you-go pricing for many cloud services. For TakTo, the practical benefit was being able to switch off idle environments and bring them back online when needed. That gave the team more control over compute usage as demand changed.

The solution is also highly flexible, which in turn allows our team to act faster and shorten the time to market for new services.

— Dagmara Majdak, Head of Project Development at TakTo

Customisation

Spyrosoft designed the AWS environment around TakTo’s existing application. Virtual machines give teams control over choices such as the operating system and software configuration. A fully managed service can reduce routine IT operations where the team needs less control over the underlying infrastructure. The choice depends on the application’s dependencies, data protection needs, and what the team needs to configure itself.

Your next stage of growth starts with infrastructure that can support it 

Learn more about our cloud services

How Spyrosoft migrated TakTo to AWS

Let’s get back to TakTo’s case study. The AWS migration required careful planning, detailed architecture design, and testing at every stage. TakTo operates around the clock, and thousands of people visit its website every day. Customers had to be able to use the application throughout the move without noticing any disruption.

Moving and testing workloads in stages

We used a phased lift-and-shift approach, also known as rehosting. It’s one of the seven migration strategies AWS describes and involves moving workloads with minimal changes to the application. For TakTo, the main measure of success was whether customers could still apply for loans and manage repayments throughout the move. We started with smaller databases and internal environments to test the new setup before moving the core databases.

Marcin Szremski, a DevOps specialist on the migration team, explains that the team first set up the virtual servers and supporting infrastructure, then turned its attention to the application. Once the smaller components were in place, the team could simulate how they would run in production and test how the system worked as a whole.

Backing up and migrating TakTo’s core databases

The final stage of the AWS migration involved moving TakTo’s core databases. Their size and complexity made them the most technically challenging part of the move. Before the final data transfer, we backed up the databases so the team could access the backups and restore the data if any service failed during the cutover.

We completed the cutover in a single evening, with the team working in shifts. Each developer was responsible for one step and waited for the all-clear from the person handling the previous step before starting.

takto case study

What changed for TakTo after the AWS migration

The project finished three weeks ahead of schedule. TakTo’s customers and staff continued to use the platform as usual throughout the move.

After the migration, TakTo no longer needed its physical servers. The team could add virtual machines as demand grew and switch off individual environments when they were idle.

This lets us save money when we’re not using these environments. The solution is also highly flexible, which in turn allows our team to act faster and shorten the time to market for new services.

— Dagmara Majdak, Head of Project Development at TakTo

Mateusz Gralak, Spyrosoft’s project manager, saw the migration as a step towards helping TakTo compete with leading companies in the Polish financial market.

Application maintenance and automated monitoring

After the move, Spyrosoft continued to maintain the application and used the automated monitoring tools introduced during the migration to track some operations.

What the future holds for cloud in financial services

Customers increasingly expect financial services to be online and in sync at all times, and financial companies face growing pressure to modernise their infrastructure. Cloud migration projects like TakTo’s are the direction Spyrosoft wants to explore further, and the company already works with clients asking for similar solutions for their financial infrastructure.

As Sławomir Podolski, Chief Operating Officer at Spyrosoft, says:

We’re really satisfied with how the migration projects are carried out, and that’s definitely the direction we want to explore more going forward.

Planning an AWS migration for your fintech platform?

Moving to AWS starts with deciding which workloads to migrate first and how to keep your platform available during the move. Explore our cloud services and see how we can help you plan your AWS migration while keeping the services your customers rely on available.

Before you begin, explore our guide to building a cloud migration strategy to help you define priorities, assess application dependencies, and plan each stage of the move.