There's certainly a bunch of companies that will make you part data on demand for Altium designer.
But the issue with "build and maintain company wide Altium component library/database" is that there's a bunch of different approaches (starting from Vault, svndblibs, dblibs, dblinks, managed intlibs, managed libs in a version control system, all the way down to just having a ad-hoc sch and pcb library files for each project) each valid for different purposes. Altium is extremely flexible in this area.
And then the particular conventions/standards you want for the component and footprint parts are another whole thing to consider.
Knowing the business requirements and then having an overall workflow that designers are happy with is the key to understanding the details of what you want to build.
First up, it would be good for you to have a think about what kind of work your business is doing - how many designs they plan on making a year, how big and complex the designs are, if the designs will be related by parts and even circuit structure, are they for internal use or contracted designs, and how info related to them needs to be tracked and maintained, and what info is important for a parts database. Also, will you stock parts, and therefore also need stock tracking functionality somewhere? And since you have an orcad library/database, does this new altium library/database need to be linked with or copied from, or even sharing live/verified data back and forth with the orcad one?
Then with the business needs in mind, you chat with your existing engineers and ask them what things they find are important for the workflow that they want to follow, and how that workflow will meet the company's needs. And then document that workflow & its business requirements coverage.
Then you can talk about options for what the solution might need to look like, and start to look for some company who can implement from there.