Those of us who've been around Project Management and ITBM long enough are well acquainted with the ms project import utility:

ServiceNow is very careful to advise us of the limitation of an MSProject import, but the fundamental weakness of this tool is its inaccessibility. It is precisely because the import is so limited that it's code should be deployed in the platform like all other components, and not hidden in inaccessible depths.

Why does hidden import code adversely effect ITBM implementations?

1) Every serious PMO will want to import projects2) PMOs tend to be more open to straddling multiple tools, but not over years.3) Serious PMOs can have projects that span years (see 2)4) The gaps between SN and MSProject mean different customers will address the gaps differently.

5) Reasons 1-4 mean each implementation may require special import protocols.\