Migrate off Basis Theory
We know business goals and technical needs change over time. We get it. More importantly, we want to make sure you have what you need to move off of Basis Theory and just as quickly as we've helped you safely build your products and protect your data. This guide will walk you through moving your PCI compliant data to another compliant service provider and options to move all of your non-PCI data into your database or another vault.
If you need help with your migration plan - please reach out.
Before migrating data out of Basis Theory's systems, you should confirm that the desired location meets all requirements for the underlying data type. For example, moving your card data off of Basis Theory will require you or your new provider to be Payment Card Industry (PCI) Level 1 compliant.
Create an Application
To move all of your data quickly, you'll want to create a Private Application with all permissions within the Tenant you're looking to migrate. Keep in mind this Application will have the highest level of access to your data, so you'll want to secure the API Key with the highest level of security possible as you migrate.
Click here to create an Application with all permissions.
Migrate Data
There are three recommended ways to migrate your existing Basis Theory data to a new location.
Read each section carefully, as certain methods may not be ideal for certain types of data or situations.
1. Proxy
Using our Proxy is the simplest path to migrating your data to another API-based service provider. Proxy enables you to forward your tokens to a new provider without the plaintext data touching your systems.
The following example provides a pattern for proxying your plaintext data to a new provider and storing your new provider's identifiers in your database. The array of tokens is an example of data you've stored in your database - replace this by querying your database.
import axios from "axios";
async function migration() {
const rowsFromDatabase = [
{ name: "test", ssn: "fc88408b-d031-49c6-abd9-9e53589a6091" },
{ name: "test", ssn: "c35f271e-0338-45fb-a036-c36a0e290ab7" },
// .. more rows of data
];
rowsFromDatabase.forEach(async (row, i) => {
const token = await axios.post(
"https://api.basistheory.com/proxy",
{
value: `{{${row.ssn}}}`,
format: "UUID",
},
{
headers: {
"BT-PROXY-URL": "<https://api.new.provider/secure>",
"BT-API-KEY": "key_here",
},
}
);
rowsFromDatabase[i].ssn = token.aliases[0].alias;
});
//save rowsFromDatabase to save the raw values back into your database
}
2. Export all of your data
Depending on your situation, you may want to export your data directly into your database instead of moving directly to a new Tokenization provider. When you do this, you'll want to consider encrypting the data you're exporting to keep the security of your data at the same level Basis Theory has provided you.
The following example shows how you can use the Retrieve a Token endpoint to pull back tokens you have stored within your database. The array of tokens is an example of data you've stored in your database - replace this by querying your database.
import { BasisTheory } from "@basis-theory/basis-theory-js";
async function migration() {
const bt = await new BasisTheory().init("key_here");
const rowsFromDatabase = [
{ name: "test", ssn: "fc88408b-d031-49c6-abd9-9e53589a6091" },
{ name: "test", ssn: "c35f271e-0338-45fb-a036-c36a0e290ab7" },
// .. more rows of data
];
rowsFromDatabase.forEach(async (row, i) => {
const token = await bt.tokens.retrieve(row.ssn);
rowsFromDatabase[i].ssn = token.data;
});
//save rowsFromDatabase to save the raw values back into your database
}
3. Reactors to move your data to a new provider
If the above two examples don't provide the flexibility you're needing as you switch providers, you can take advantage of our Reactors. Reactors are serverless compute services allowing Node.js code hosted in Basis Theory to be executed against your tokens completely isolated away from your existing application and systems.