Home Features Use cases Integrations Developers Pricing Partners Team About Contact Log in Start free trial
Home / Migration guide
Migration guide

Move your work into TaskSync.

Import from ProofHub, Trello, Jira or a spreadsheet, so your team picks up where it left off.

Step by step

Four steps to a smooth move.

1

Pick your source

Owners and admins open Settings → Import Data and choose where your work is now.

2

Connect or upload

Connect with an API key (ProofHub), or upload the export file from your current tool.

3

Check first

Match people and columns, then see what will happen before anything is created.

4

Import & invite

Run the import, check the result in Import History, then invite your team.

What comes across

Where you can import from.

Every file import shows a dry run first and matches people to your existing members, so nobody is emailed by surprise.

ProofHub

How: Enter your ProofHub company address and API key (in ProofHub under My Profile → API). Choose the projects and data to bring, match ProofHub people to TaskSync members or create them, then import. You can pause and continue a long import.

Brings across: People, groups, categories, labels and custom fields; per project: task lists, tasks and sub-tasks with assignees, dates, estimates, priority and stage, task comments and attachments; timesheets and time entries; discussions; files and folders; events and milestones; notes.

Good to know: Files can stay linked to ProofHub or be downloaded into TaskSync.

Trello

How: In Trello, open the board menu and export it as JSON. Upload the file (up to 25 MB and 5,000 cards) into a new or existing project.

Brings across: Lists become task lists, cards become tasks (title, description, dates, completed), checklist items become sub-tasks, plus labels, members as assignees and, if you choose, comments.

Good to know: Attachments and Power-Ups are not imported. People are matched to existing members by name or email; nobody is emailed.

Jira

How: In Jira, export your issues as CSV (all fields). Upload the file (up to 10 MB and 5,000 issues), match the columns, and choose how to group issues into task lists: by status, epic, sprint or one list.

Brings across: Issues and sub-tasks, issue types, priorities, labels, assignees, start and due dates, estimates, descriptions and comments. Statuses can become board stages. The Jira key is kept.

Good to know: Attachments and worklogs are not imported.

CSV / Excel

How: Download the template or use your own sheet (.csv or .xlsx, first sheet, up to 5 MB and 5,000 rows). Match the columns, choose the date format and the project, then import.

Brings across: Task title, description, task list, start and due dates, assignees, labels, estimate, completed and task type.

Good to know: Sub-tasks, comments, attachments and time entries are not part of a spreadsheet import.

Coming later: Asana, monday.com, ClickUp. Using something else? Tell us.

★
Need a hand? We’ll do it with you.

The Enterprise plan includes guided migration — our team helps move your data across. On any plan, tell us what you use and we’ll point you to the right importer.

Request migration help → See plans
✓