Back to all case studies

Public Sector Software

How a software provider moved its analytics to AWS and got data to its teams sooner

A software provider for the public sector ran its analytics on Azure, where data reached internal teams late and the setup was hard to maintain. The company wanted it on AWS, so we rewrote the workflows, migrated the warehouse and rebuilt the data lake. Data now reaches internal teams sooner.

About 50

tables and schemas migrated to the new warehouse

5+

complex pipelines ported and validated in AWS

Sooner

data reaches internal teams for analysis

Challenge

Data reached internal teams late, the setup was hard to maintain, and the old workflows could not move to AWS unchanged.

What we built

Rewritten workflows, a migrated warehouse and a rebuilt data lake on AWS, with version control and automated tests.

Result

Analytics running on AWS, with data reaching internal teams sooner.

The challenge

The company ran its analytics on Azure, and delays in data delivery meant internal teams waited longer for results. The setup was hard to maintain and lacked modern version control and automated testing. The company wanted its analytics to run on AWS, but the old workflows could not move there unchanged. The processing logic had to be rewritten alongside the move of the storage and warehouse data.

What we built

  • Rewrote the old pipeline logic as new workflows that run on AWS. Along the way, we found and corrected long-standing inaccuracies and inefficient processing in the original workflows.
  • Migrated about 50 tables and schemas to a new warehouse on AWS, and moved the data lake's landing and storage layers there too. The 5+ complex pipelines and the migrated tables were validated in AWS.
  • Introduced version control, reviewed changes, automated tests and quality gates, with documentation versioned alongside the code. The team now has repeatable checks for later changes to the platform.

How the data flows

Before, on Azure

Synapse workflows
Azure Data Lake Storage
Existing warehouse
Moved to AWS, with workflows rewritten

After, on AWS

Airflow on MWAA (Python)
Amazon S3 data lake
Amazon Redshift warehouse

The outcome

The company now runs its analytics on AWS, with rewritten workflows, a new warehouse and a rebuilt data lake. Data reaches internal teams sooner, and long-standing inaccuracies in the old workflows were corrected along the way. Source code, documentation and automated checks are now managed in version control.

Systems & technologies

AWS MWAAApache AirflowPythonAmazon RedshiftAmazon S3SQLGitHub

Before vs after

Before
BeforeAnalytics on Azure, with workflows that could not move unchanged
AfterAnalytics on AWS, with workflows rewritten and validated
BeforeData reached internal teams late
AfterData reaches internal teams sooner
BeforeHard to maintain, lacking modern version control and automated tests
AfterVersion control, reviewed changes, automated tests and quality gates

Get in touch

Planning to move your analytics to a new cloud?

If your workflows cannot move to the new cloud unchanged, we can rewrite them, migrate your warehouse and data lake, and validate the migrated pipelines and tables.

Email us directly

sales@3alica.com