What is the most efficient method for manually migrating Jira projects?

[Rob Horan]

Let's assume we only need to move the project configs - issues types, workflows, schemes, etc, and not the issues.

Also forget Project Configurator.  End user ain't buyin'

Is there a way that cuts out at least part of the manual effort of manually recreating the product, or at least a preferred order of work?

[Joe Pitt]

No. Since you aren't moving the issues I'd verify you actually need all the old workflows, schemes, etc. and when you currently have can't be used. Otherwise you're just building up a new project from scratch and whatever order is used is irrelevant. 

[Rob Horan]

Everything is new. It's all needed.

[Rob Horan]

Well, it's possible to export q workflow and reimport, right?  Wouldn't that at least eliminate the need for manually recreating it? I guess that's the only effort reducing piece.

[Joe Pitt]

It isn't an easy process. Check out this link

https://confluence.atlassian.com/adminjiraserver071/sharing-your-workflow-802592731.html?_ga=2.257933259.1556066392.1579621030-437329637.1579198032#Sharingyourworkflow-Exportingyourworkflow 

[Rob Horan]

Thanks.  I have already suggested they incorporate this into their process, so at least they don't have to recreate their workflow, which is.... large.

Still there is so much more that will need to be created manually.