His manager’s plan? Ask Michael to stay on part-time after retirement. But Michael was planning to move to Florida, and postponing the problem wouldn’t solve it.

So, they called R2i.

As one of the only companies in Quebec still training developers on RPG, R2i stepped in to preserve the knowledge, support the existing systems, and prepare the organization for a smooth transition.

The RPG knowledge gap is here—and growing

Across Canada, IT leaders are facing a difficult reality: key developers and system architects, many of whom built and maintained RPG applications for decades, are approaching retirement. And their expertise is walking out the door with them.

IBM i systems running RPG still support mission-critical operations in sectors like finance, insurance, healthcare, and manufacturing. Replacing them isn’t always feasible. But training new talent is easier said than done.

So what’s the best move? Should you invest in training new RPG developers, or modernize your systems entirely?

Train or modernize? Here are the pros and cons

There’s no one-size-fits-all answer—but there is a strategic decision to be made.

Option 1: Train new developers on RPG and IBM i

Pros:

• Preserves decades of business logic and customization
  
• Avoids the cost and risk of replatforming
  
• Keeps existing systems stable and secure
  
• R2i provides internal training for its staff when needed, but we don’t currently offer RPG training. 

Cons:

• RPG talent is increasingly scarce
  
• Training takes time and commitment
  
• Systems may still need modernization eventually

Option 2: Replace legacy systems with modern tech

Pros:

• Opens up access to broader talent pools familiar with modern languages
  
• May enable faster innovation in the long term
  
• Could simplify architecture or eliminate technical debt

Cons:

• Expensive and complex to replicate legacy functionality
  
• Long transition period with risk of disruption
  
• High learning curve and training needs for existing staff

R2i’s perspective: Choose with eyes wide open

At R2i, we’ve worked with many organizations navigating this exact question. Our advice: Don’t modernize just to avoid training.

Rebuild your applications only if they are no longer functional, cost-effective, or aligned with your future goals.

Otherwise, it is more strategic to preserve and support what you already have—while developing a clear plan to pass on institutional knowledge.

Your plan should address how you will:

• Absorb institutional knowledge from retiring staff
• Support and improve your RPG and IBM i applications
• Train new specialists to sustain your systems long-term

There are a few partner organizations who can help you with this. In Quebec, R2i and only one other team offers this service. 

If you’re uncertain how to preserve and pass on your institutional knowledge, seek out support from experts who not only understand RPG systems but also how they fit into your broader business processes and how best to train incoming developers.

R2i is here to help you talk through your options so you can protect your systems, your knowledge, and your peace of mind. Reach out if you would like support.