Getting started

Connecting accounts with API tokens vs OAuth

In the Connect step, DatMig needs permission to read your source platform and write to your target. You can grant that in one of two ways: an API access token or OAuth. Either grants the same access; pick whichever is easier for your setup.

API access token

A personal API token is a key you generate in the platform's own settings and paste into DatMig. DatMig recommends you to use it when possible since OAuth is not available on all platforms.

Each migration's Connect screen links to exactly where to find the token, for example, in ClickUp it's found under Settings → Apps → API Token, or Monday.com under Developers → My Access Tokens. You can also click on each migration here to know more.

OAuth

OAuth signs you in and hands DatMig a scoped, revocable permission; no password is ever shared. You need to generate a Client ID and Client Secret in the respective platform's own settings and paste them into DatMig.

Each migration's Connect screen links to exactly where to find the Client ID and Client Secret, for example, in ClickUp under Settings → Apps → OAuth, or in Monday.com under Developers → OAuth. You can also click on each migration here to know more.

Good to know

• All credentials are scrambled and stored encrypted. Expired OAuth tokens refresh automatically during long migrations.
• You can disconnect a connection at any time from the Connect step.
• Connections are remembered in your workspace, so any further migration skips this step.