→
Workfront → ClickUp Coming soon
Migrate your Workfront space to ClickUp: folders, projects, tasks, and so on, through an easily guided user interface.
What gets migrated
- Projects (as lists or folders)
- Tasks & nested tasks (as subtask chains)
- Statuses (built-in and custom codes)
- Priorities
- Custom form (DE:) fields
- Assignees (matched by email)
- Notes (as comments)
- Documents (as attachments)
- Hours (as time entries)
- Predecessors (as dependencies)
How the hierarchy maps
- Each Workfront project becomes a list in the target space, or a folder holding a “Tasks” list.
- Workfront's arbitrary task nesting becomes ClickUp subtask chains.
- Statuses and custom fields are discovered from the selected projects' tasks when mapping loads.
Prerequisites
- Adequate permissions in Workfront; see the Before the migration section below.
- Adequate permissions in ClickUp; 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 |
|---|---|---|
| Workfront | API access token | Paste an API key from Workfront under Setup → System → Customer Info, and set your instance API base URL (https://<company>.my.workfront.com). Click here for more information. DatMig connects to Workfront with an API key. |
| ClickUp | API access token | Generate a personal API token in ClickUp under Settings → Apps → API Token. Click here for more information. |
| OAuth 2.0 | Create an OAuth app in ClickUp (Settings → Apps → Create new app) to get a Client ID and Secret, then register the callback URL DatMig shows you. Click here for more information. |
Permissions
- Permissions in Workfront: 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 ClickUp: 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
- A Workfront API key and your instance URL (the API lives on your own domain).
- ClickUp custom fields must exist in the target space before the run.
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.