Cloning a module using the Clone Module tool provided by Ivanti is not suitable for this case (As far as I am aware this tool can be used within the same database - no database destination can be selected during the cloning process). The best thing to do in such cases (in my opinion) is to use Design Transfer in the following order:
- All the attributes with filters
- All other attributes
- Ordered Lists
- Reference lists
- Roles and Groups
- Queries only, no filters
- Response Levels
- Self Service
(This list is taken from another post - Help with Design Transfer tool )
I suggest you backup both databases prior applying any changes. There might be some manual actions you may need to take afterwards like setting up the default processes.
Locking and transferring modules
If you are logged in to Console as a user who has their culture set to the default language, you can export locked modules using Design Transfer so that they can be imported into another database.
https://help.landesk.com/docs/help/en_US/LDSD/10.0/Default.htm#038 2016 New Features/CreateModules.htm%3FTocPath%3DRelease%2520documentation%7CNew%2520Features%25202016%7CService%2520Desk%25202016%7C_____6
This will only work for modules that are created manually and not OOTB modules. For example, I created Project Management module and I was able to transfer it between multiple databases with no issues. You could give that a shot and it will definitely work!