Eximus logo

Case study · ITSARC

Modernizing ITSARC's credit risk platform without disrupting operations

How Eximus modernized a credit risk platform without disrupting reporting cycles or integrations.

Result in operation

Kept reporting and integrations stable while moving the platform to a maintainable, lower-risk architecture.

Client
ITSARC
Context
Banking & Finance
Service
GeneXus modernization for regulated systems

The case at a glance

01 · Challenge

Upgrade under regulatory deadlines without breaking reporting or integrations.

02 · Intervention

We prepared, rehearsed and tuned the migration to protect reporting.

03 · Outcome

Kept reporting and integrations stable while moving the platform to a maintainable, lower-risk architecture.

A credit risk platform built on older GeneXus versions needed to move to supported releases without interrupting reporting cycles. Eximus executed a controlled modernization to restore supportability, reduce operational risk, and keep performance steady for a regulated banking team.

Client and context

The client delivers risk analytics and regulatory reports, dependent on timely data refreshes.

  • Sector: Banking and finance.
  • Team: Mid-sized platform group with tight reporting SLAs.
  • Key systems: GeneXus (legacy to supported versions), SQL Server, ETL and BI jobs.

Challenge

Upgrade under regulatory deadlines without breaking reporting or integrations.

  • Complex ETL and reporting jobs with tight windows.
  • Performance risk on heavy SQL workloads.
  • Limited tolerance for downtime during reporting cycles.
  • Need for evidence for auditors and stakeholders.

Our approach

We prepared, rehearsed and tuned the migration to protect reporting.

  • Inventoried KB objects, jobs and integrations to map risk.
  • Built a parallel environment for tests and rehearsal cutovers.
  • Tuned SQL queries and schedules after migration to meet reporting windows.
  • Established deployment scripts and rollback plans.
  • Coordinated with client teams for change windows and validation.

Results

  • Migration completed on schedule and within reporting windows.
  • Reporting performance recovered and stabilized post-migration.
  • Compliance evidence produced for auditors.
  • Repeatable runbooks for future changes.

Tech & services used

  • GeneXus (legacy to supported), SQL Server, Azure DevOps/Jira for coordination.
  • Service: GeneXus Modernization.

Lessons learned

  • Early inventory of jobs and integrations avoids surprises in cutover.
  • Rehearsal cutovers reveal timing and performance gaps before production.
  • Post-migration tuning is essential to regain reporting SLAs.

Next step

If your GeneXus-based reporting platform needs to upgrade without breaking SLAs, we can map a phased plan and rehearsals. Contact us to start.

Continue exploring

More decisions in similar contexts