Mapping how-tos

Choosing a hierarchy mapping

Different platforms organise work differently: Wrike nests projects & folders freely, ClickUp has a fixed Space → Folder → List → Task hierarchy, Asana doesn't allow projects to nest within each other, etc. The hierarchy mapping decides how your source structure is reshaped to fit the target.

The main choice

• For most migrations you choose what your top-level source container becomes in the target.
• You then choose what lower-level source containers become in taget. In some cases, because of your choice on the top-level containers, constraints are applied on what lower-level containers can become in target.
• In cases where the target hierarchy can't be as deep as the source, the deeper levels either flatten (items move up to the deepest allowed level) or become tasks/items.

Tips

• Map your hierarchy based on how you will work in the target.
• Subtasks always keep their exact nesting regardless of the container choice.
• If you are unsure, run a small test and see which mapping reflects best in the target, then use it in the full migration.