If you bring in someone who is smart, pragmatic, and interested in a nice indoor job with good pay, they're more interested in the specialized job training and position that comes with it.
Someone I knew made the tongue in cheek retirement joke that "where else could I learn COBOL and mainframe in university, and never learn anything else until I retired?"
The jokes I heard were about ADD 1 TO COBOL GIVING COBOL, following the convention established by C++.
Recent versions of the COBOL standard, like Fortran and Ada, include object-oriented extensions.
I always assumed it'd be `POST-INCREMENT COBOL BY 1`
If your skill is in demand, get training in that domain.
If your skill belongs to a niche, be careful, consider how you can reuse the knowledge you are aquiring.
Their reasoning was it would be easier to train new individuals and work them up, using senior staff as trainers and escalation points than to try and find existing COBOL programmers. They started the pay off quite well and were able to pull in some highly talented people. They approached it almost like an apprenticeship, only with programming as the trade.