@Yashvant Ghonsikar, I would say that it depends on what you mean by all data. Perhaps, for your dataset, yes, which might not be true for others. When moving between two different project types, likely not as they have distinct features. SLAs, for example, it's a service project specific feature and won't be carried over to other project types when moving or migrating data.
I believe you're referring to migrating issues within the same site, and moving issues would be one approach you're looking at. If so, they can be very different. There are a few distinct use cases, like migrating from team-managed to company-managed projects, using CSV export/import, etc., depending on the limitations or requirements driving the move.
The moving issue action is similar. The process differs from project to project. Project-specific data, such as fixVersions, require an exact match in the target project. As another example, If you have restricted comments, you need to ensure a proper permission configuration on the target, and the list goes on and on.
Beyond doing your research, as you're doing. Test, test, test, test... You can't go wrong when putting it into action.
I hope that helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.