How Credit Agricole Bank Polska solved the Atlassian Server end-of-life challenge with a strategic move to Data Center

What happened and why it matters

For Credit Agricole, the end of Atlassian Server support posed a major compliance and operational risk. The shift to Atlassian Data Center solved this while adhering to strict local data laws.

• Mandatory upgrade: The bank migrated Jira and Confluence to the Data Center (DC) edition due to Atlassian ending support for Server-based products.
• Complex plugin adaptation: The transition required adapting 29 custom plugins to function on the new architecture.
• Operational continuity: The migration was executed without disrupting the bank's daily operations.
• Future-proofing: The bank gained access to native DC features (like Advanced Roadmaps project archiving) and high-availability architecture.

About Credit Agricole Bank Polska

Credit Agricole Bank Polska is a universal bank that has operated in the Polish market for 30 years. It is part of the Crédit Agricole Group, one of the top 10 largest banks globally, serving retail, corporate, agriculture, and SME sectors.

Balancing end-of-life with Polish banking laws

With Atlassian discontinuing Server support, staying on the old infrastructure meant losing critical security updates. However, the bank faced a hard constraint: due to strict regulations from the Polish Financial Supervision Authority (KNF), data localization was mandatory.

Moving to the Cloud was legally impossible; data had to remain on their own infrastructure. They also had to migrate an extensive logistical footprint consisting of over 2,000 active users across both Jira and Confluence, plus 29 custom-built plugins essential to their workflow.

Credit Agricole's path to Data Center

We implemented a multi-node, Data Center architecture.

• The tech stack: The solution was built using Docker, NetScaler (for load balancing), Red Hat Linux, and NFS.
• Phased rollout: The project started with a technical audit to estimate workload, followed by a test migration where the 29 custom plugins were adapted to the DC environment, and concluded with the final production migration.
• Enhanced security: The team utilized Data Center's native bandwidth throttling feature to strictly monitor and control the speed of incoming and outgoing traffic, a crucial requirement for banking security.

Migration Impact: Continuous uptime, full compliance

While exact financial savings weren't disclosed, the technical and operational KPIs post-migration reflect a highly successful deployment:

• 0 minutes of downtime: The multi-node load balancer setup allowed for system maintenance, updates, and the migration itself to occur with zero interruption to employees.
• 2,000 users successfully migrated: Full transfer of all accounts across both Jira and Confluence.
• 29 custom plugins retained: All proprietary client plugins were successfully adapted to the Data Center version without loss of functionality.
• 100% KNF Compliance: Maintained strict adherence to Polish data localization and security laws by keeping infrastructure on-premise.