# Migratly

> Migratly migrates data between SaaS tools by reading both APIs, deriving the field mapping,
> and showing you exactly what will and will not carry across before anything is written.
> A new source-to-target pair is a written description rather than a new codebase.

Migratly exists to close the gap between "the records arrived" and "the work survived". Most
migration tools move the easy 80% and silently skip custom fields, cross-references, parent-child
structure and attachments. Migratly reads the live schema on both sides, produces a coverage report
where every field mapping is labelled full, partial, lossy, workaround or dropped, and stops to ask
when the right answer depends on your instance. The source system is read-only for the entire run;
execution happens in dependency waves, is idempotent, resumable from a cursor, and written to an
append-only audit log.

Currently supported pairs: Google Drive to OneDrive, Jira to Linear, Jira to Monday.com, Jira to Notion, Linear to Jira, Notion to Confluence, OneDrive to Google Drive, Pipedrive to HubSpot.

## Migration guides

- [Google Drive to OneDrive](https://migratly.dev/migrate/gdrive-to-onedrive.md): entity map and field-by-field coverage — 8 entity types, 22 field mappings, 7 carrying across intact, 13 flagged before the run.
- [Jira to Linear](https://migratly.dev/migrate/jira-to-linear.md): entity map and field-by-field coverage — 13 entity types, 113 field mappings, 54 carrying across intact, 59 flagged before the run.
- [Jira to Monday.com](https://migratly.dev/migrate/jira-to-monday.md): entity map and field-by-field coverage — 13 entity types, 70 field mappings, 35 carrying across intact, 30 flagged before the run.
- [Jira to Notion](https://migratly.dev/migrate/jira-to-notion.md): entity map and field-by-field coverage — 8 entity types, 58 field mappings, 27 carrying across intact, 30 flagged before the run.
- [Linear to Jira](https://migratly.dev/migrate/linear-to-jira.md): entity map and field-by-field coverage — 11 entity types, 45 field mappings, 28 carrying across intact, 16 flagged before the run.
- [Notion to Confluence](https://migratly.dev/migrate/notion-to-confluence.md): entity map and field-by-field coverage — 8 entity types, 53 field mappings, 24 carrying across intact, 28 flagged before the run.
- [OneDrive to Google Drive](https://migratly.dev/migrate/onedrive-to-gdrive.md): entity map and field-by-field coverage — 8 entity types, 21 field mappings, 7 carrying across intact, 10 flagged before the run.
- [Pipedrive to HubSpot](https://migratly.dev/migrate/pipedrive-to-hubspot.md): entity map and field-by-field coverage — 8 entity types, 18 field mappings, 7 carrying across intact, 11 flagged before the run.

## How it works

- [Migratly: what it is](https://migratly.dev/blog/what-migratly-is/): Migratly is a migration engine in which a new source-to-target pair is a description rather than a codebase. What it does, and what it deliberately doesn't.
- [Five ways a field can survive](https://migratly.dev/blog/five-ways-a-field-can-survive/): Fully supported, partially supported, supported through a workaround, impossible in the target, or needing a human decision. Why every mapped field carries one of these labels, and why anything short of the first one stops and asks.
- [The nth connector pair should cost almost nothing](https://migratly.dev/blog/nth-connector-pair/): If every source-to-target pair is its own codebase, the hard parts of a migration never get funded. What changes when a pair is a description instead of a project.
- [What actually happens during a migration](https://migratly.dev/blog/what-happens-during-a-migration/): Start to finish, in the order you'd experience it: connecting both systems, discovering the schemas, reviewing the coverage report, confirming the lossy fields, and what dependency waves means when you're watching one run.

## Product

- [Migratly home](https://migratly.dev/): what the engine does, the integrations it supports, and how a run is structured.
- [All supported migrations](https://migratly.dev/migrate/): every pair with its coverage report.
- [Start a migration](https://app.migratly.dev/): the application itself.

## Optional

- [Full text of everything above](https://migratly.dev/llms-full.txt): single-file corpus, for ingestion.
- [Demo videos](https://www.youtube.com/@migratly_dev): recorded end-to-end runs.