Skip to main content

​
Overview

Terminal supports importing credentials from other telematics aggregators or your direct integrations. This allows you to migrate existing connections without manual end-user re-authentication. The process involves exporting your current credentials, optionally adding custom identifiers, and securely sharing the file with Terminal to complete the migration.

​
Migration Steps

Below are the steps to migrate your connections to Terminal.

​
1. Prepare Credentials

Export your existing connection credentials from your current system. If you’re migrating from another telematics aggregator, request a bulk export from them. If you’re migrating from direct integrations, compile your credentials into a structured format. The export should include all non-OAuth integrations.

​
2. Add Custom Identifiers (Optional)

If you associate connections with internal identifiers in your system, add an external_id column to the exported file. This allows you to maintain your existing identifier mappings after migration. Learn more: Custom Identifiers

​
3. Share the File Securely

Send the exported file to us through your preferred method - such as encrypted email or another secure method. We’ll confirm receipt and validate that everything is complete.

​
4. Terminal Runs the Migration Script

Once we have the file Terminal will run a script to import each set of credentials. This process validates the credentials and creates new connections in Terminal.

​
5. Verification

Our team will:
  • Confirm that data is syncing correctly.
  • Run a quick validation to ensure the data matches what was previously coming through your prior system.

​
6. Wrap-Up

After successful migration:
  • You’ll receive a confirmation summary.
  • You can switch your API calls to use the Terminal API in place of your previous system.

​
Limitations

​
OAuth Connections

Samsara and Motive both use OAuth to authenticate connections. If you have ownership of the OAuth applications used for these providers, it may be possible to migrate these connections to Terminal. If another party (such as a previous telematics aggregator) has ownership of the OAuth applications, we’ll need to manually re-authenticate the connections with new OAuth applications in your name.

​
Credential Structure Differences

For some providers it’s possible your current system uses a different structure for credentials than Terminal expects. In some cases this may mean specific connections or providers are not able to be migrated automatically and may require additional coordination.
⌘I