Why isn't there a json based schema standard at this point? At the very least you import once, clean it up once, save the clean version, and then upload that one going forward?
The stupid thing as well is most of it is SAAS Taleo, so there should be a button that says "Share my upload of CV data from Company A to Company B". It's not impossible to move the data from one instance to another.
But nobody uses them, because nobody uses them. LinkedIn and other proprietary recruitment services like TeamTailor want to keep all the details locked in - there's no advantage to them to allow you to mass import/export candidate details.
No one uses them because I don't think I've even seen an application process that offers it. Mind you, I rarely get to the end of those because that's why I have a CV.
That said, why doesn't LinkedIn throw its weight behind this? In that context, it would make sense to have and maintain my CV there. With some sort of authorization confirmation that would let a 3rd party import it into their system?
"Before I tell you about my work experience, let me relate a wonderful story about what work means to different people around the world. My great-grandmother was born in ..."
There's got to be a smarter way.