Every pair below has a full entity map and a field-by-field coverage report, generated from the connector spec the engine actually runs. Open one to see exactly what carries across and what doesn't — before you connect anything.
The folder tree carries across cleanly; the friction is Google-native file formats and what OneDrive will let an API set.
Linear is flat where Jira is nested, so the shape of the work changes on the way across.
Monday organises work as boards inside folders, so one Jira project fans out into several boards.
Notion has no issue type, so a Jira project becomes a database and every issue becomes a page inside it.
Jira is project-centric and unusually restrictive over REST, so several natural mappings run as deliberate workarounds.
Confluence is a strict tree — one space, one parent per page — while Notion is a graph, and most of the work is in reconciling the two.
The same trade-offs as the other direction, mirrored: format conversion is now opt-in rather than forced.
Two flat CRMs, so there is no hierarchy to rebuild — the work is object mapping and rebuilding associations afterwards.
A new source-to-target pair is a written description in Migratly, not a new codebase — which is why the catalogue grows the way it does. If the two systems you need aren't listed, tell us which ones and we'll tell you honestly what it would take.