Anyone that wants to use TYOOL 2016 age DVCS features should also switch. Like changing history yet still keeping a record of the original one (hg evolve).
Git completely owned all other DVCS with good branching. 10 years ago. But now it's time to move on to better tools.
Some companies even have Git, Mercurial, and SVN, working all together under centralized repository management.
Both git and mercurial can talk to "non-native" remote servers.
IIRC mercurial can talk to subversion and git (with hg-git).
Git can talk to subversion, cvs, perforce, mercurial (there are multiple tools for the latter, and I'm the author of one of them), bzr, and maybe others.
If things don't work smoothly in any of those cross-VCS configurations, my belief is that issues should be filed and fixed.
Working in a big firm adds overhead, yet has certain benefits (resources, etc.). That's a whole different topic though.