Asana migration services

Yes. Cirface migrates Trello boards into Asana, including cards, checklists, comments, attachments, and members. Trello's own export drops most of this. We rebuild the board structure as proper Asana projects and sections rather than a flat task list.

Yes. Cirface migrates Monday.com boards, items, subitems, updates, files, and columns into Asana projects, tasks, subtasks, comments, attachments, and custom fields. Monday's guest accounts often complicate user mapping, so we map users explicitly as part of the migration.

Yes. Cirface migrates Smartsheet data into Asana. Smartsheet behaves like a spreadsheet rather than a project tool, so its data needs real restructuring on the way in. We rebuild sheets as Asana projects with proper task hierarchies rather than importing flattened rows.

Cirface also migrates from Wrike, Excel and CSV files, and Asana to Asana, either workspace to workspace or domain to domain. ClickUp and Airtable support is on the way.

Tell us what you are running. Our migration tool is built in-house, so we can extend it to new sources where the scope justifies it. Send us the tool and rough project and item counts, and we will tell you honestly whether we can help.

We run our analyzer across the projects you select. It reports exact counts of tasks, subtasks, total items, custom fields, users, comments, and attachments. That count is what we price the migration from, so your estimate reflects your real data rather than a guess.

No. The analyzer runs only on the projects you choose. It can be run live with your team watching, so you see exactly what is being read and what the report contains. Nothing is copied out of your systems during the assessment.

Tasks and subtasks up to five levels deep, comments in the right order, attachments, dependencies, custom fields, assignees, followers, sections, and dates. Each migrated item keeps a reference to its original ID, so any record can be traced back to its source.

Yes. Both come across. Comments stay threaded with the tasks they belong to, and attachments move with their tasks rather than landing in one unsorted folder. A manual CSV export typically loses comments entirely and separates attachments from their context.

Yes. We migrate into projects and custom fields you already use, not only into newly created ones. We can also consolidate scattered fields into clean Asana library fields as part of the move.

No. Your team keeps working in your current tool while we migrate. Everything lands first in a staging area inside your own Asana, where we check it against the source before it reaches your live teams. You switch over once it is verified.

Most run four to eight weeks, depending on the number of projects, the item count, and how much restructuring the source needs. The assessment happens first and is the fastest part. The bulk of the timeline is mapping, validation, and getting your team ready to work in Asana.

Pricing combines a base fee, set by how many projects we build, with a per-item rate on everything we move. The rate per item falls as volume rises. We scan your source system for an exact item count before quoting, so the number is scoped rather than estimated.

Access to our migration tool is restricted to the Cirface team. We read from your source system and do not store your data in a separate database. Everything lands in a staging area inside your own Asana, where every step is logged for you to review.