→
Asana → Wrike Beta
Migrate your Asana space to Wrike: folders, projects, tasks, and so on, through an easily guided user interface.
What gets migrated
- Projects (as Wrike folders or projects)
- Sections (as subfolders or flattened)
- Tasks & subtasks (any depth)
- Completion status (to Wrike custom statuses)
- Custom fields (text, number, enum, multi-enum, date, people, checkbox)
- Assignees (matched by email)
- Comments
- Attachments (Asana-hosted and external links)
- Tags (to a Wrike custom field)
- Dependencies
How the hierarchy maps
- Each Asana project becomes a Wrike folder or project in the target space.
- Asana project sections become subfolders in Wrike project, or can be skipped so tasks in them are migrated directly into the project folder.
- Asana subtasks keep their exact nesting under Wrike parent tasks.
Prerequisites
- Adequate permissions in Asana; see the Before the migration section below.
- Adequate permissions in Wrike; see the Before the migration section below.
During a running migration
- Live migration progress
- Pause & resume anytime
- Retry failed objects only
- CSV report + full API log
Security & data storage
DatMig's servers are hosted with a public cloud provider in France and are compliant with GDPR.
DatMig migrates your data on the fly and doesn't store any of your work data. Only object IDs and names are retained, for retry and reporting purposes.
Before the migration
Authentication
Before you can migrate any data, you'll need to authenticate to both the platforms so that DatMig can access those. You can either authenticate through an API access token, or through OAuth 2.0 if the platforms support it. DatMig recommends that you use an API access token to authenticate as it's the relatively simpler and widely supported method.
| Platform | Method | How to get the credential |
|---|---|---|
| Asana | API access token | Create a Personal Access Token in Asana under Settings → Apps → Developer apps. Click here for more information. |
| OAuth 2.0 | Register an app in the Asana developer console to get a Client ID and Secret, then register the callback URL DatMig shows you. Click here for more information. | |
| Wrike | API access token | Generate a permanent API token in Wrike under Profile → Apps & Integrations → API → Create token. Click here for more information. |
| OAuth 2.0 | Create an OAuth 2.0 app in the Wrike App Console to get a Client ID and Client Secret, then register the callback URL DatMig shows you. Click here for more information. |
Permissions
- Permissions in Asana: Your account must have read permissions on all data you plan to migrate. You don't need to be an Administrator, however DatMig recommends that you get full access to the space you wish to migrate. You can only migrate what your account has access to. If your account doesn't have access to the required data, DatMig recommends that you use a Service Account that has access to the entire space.
- Permissions in Wrike: Your account must have read, write, create, edit, delete permissions in the target space. DatMig recommends that you get full access to the target space. If your account doesn't have read, write, create, edit, delete permissions, DatMig recommends that you use a Service Account that has full access to the entire space.
Preparation of source & target
- Do a cleanup of the Asana space you want to migrate. That way, unwanted items will not be migrated to Wrike.
- Create or add the needed custom fields in the target Wrike space. In the migration mapping step (see here), DatMig will let you choose Wrike custom fields to map to the Asana custom fields. Only the custom fields that are created or added to the target Wrike space will be available for selection.
- Create or add any needed workflows to the target Wrike space. DatMig will let you map Asana statuses to Wrike statuses. Statuses from Wrike account workflows and space workflows are available for selection.
After the migration
- Go through the migration report to see exactly what was migrated and what wasn't.
- Manually address any objects that failed due to target-platform constraints (for example, unsupported characters or field limits); these can't be fixed by a retry.
- If you no longer need them, delete the API access tokens or OAuth apps you created for this migration.