Move to EU Flow
A good move starts with what you have.
An automatic migration from Asana, Jira, Trello or monday.com is in preparation. The key is how statuses, people and custom fields map to the new project.
In preparation
Clarify the scope in advance.
Migration is in preparation. The importers haven't been built yet. This shows what's meant to come across, not what already works today.
Planned sources
Prepare in three steps
Review first. Then decide.
Choose a project
Select a manageable project with typical tasks and fields.
Plan the mapping
Compare statuses, owners, deadlines and custom fields.
Review the history
After a future migration, check subtasks, comments and attachments separately.
Before getting started
Good to know.
Why do I need a timeline as well as a board?
The board organises work by status. The timeline shows dates, milestones and dependencies in context.
Does Flow also show how work is distributed?
The listed capacity view displays planned work by person and week. It supports planning discussions.
Are Jira fields transferred unchanged?
An automatic migration from other providers is in preparation. Custom fields and statuses require an explicitly reviewed mapping.
Are absences from HR always taken into account automatically?
The connection is provided for in the product documentation. This page does not promise a fully configured automatic synchronisation.
