This is what we suggest to all our customers. At present, there is no escalation process from a Dev ORG to Prod ORG except manual export and import and correcting all the GUID links. This makes for an error-prone process when procedures are not followed and you have different GUID's for queues, agents, flows, and the like between the ORGS. We suggest you carve out a Dev division in the Production ORG and also make a PROD division. Have engineers work in Dev and map all the data actions, common modules, queues, etc in that division when they are developing and when you are ready, it is just a matter of saving into the PROD division and routing to it. Makes for much easier escalation, fewer errors, and costs a whole heck of lot less. You just have to make sure developers only have access to flows, queues, et al in the Dev Division.