Migrating Tokens

Auric’s token migration service provides a number of customizable ways to move tokens to and from the AuricVault® service.

Each token migration is unique and customized to match both your requirements and your current (or future) tokenization service’s requirements.

Auric can migrate all types of sensitive data: credit card numbers (PCI), tax IDs (PII), etc. We can customize both the final batch file delivered and the format for the stored/tokenized data.

Please contact sales@AuricSystems.com to discuss your batch migration process in detail.

Initial Batch Tokenization

Auric can batch import data that has not previously been tokenized. Each batch tokenization process is unique. Auric generally expects to receive an encrypted .csv text file with the following two columns:

  • ID to uniquely identify the data in your system (can be a database row id).

  • Data to tokenize.

Auric returns an encrypted .csv text file with the following two columns:

  • Unique ID from your system.

  • AuricVault® token ID.

The following diagram shows a simplified, high-level view of the initial data tokenization process.

_images/initial-tokenization.svg

Import Existing Tokens

This is a simplified, high-level view of the batch token import dataflow. Each batch token import process is unique. Auric can batch import tokens or import tokens dynamically if your current tokenization service provides an API.

Where possible, the import process preserves your existing token IDs. This allows you to migrate to the AuricVault® tokenization service without changing the data stored on your servers.

_images/migrate-tokens-to.svg

Batch Token Export

Each batch token export process is unique. From a high-level view, the process starts when you request a batch export from Auric. Auric coordinates the transfer process with the target service to which the tokens will be migrated. This includes coordinating encryption keys and batch file layouts.

Auric also coordinates with you to determine if you are storing any sort of structured data in the tokens. For example, instead of just storing a tax ID as plain ASCII text, you might store the tax ID in a JSON that includes a time and date you acquired that tax ID. Auric will review your stored data with you to ensure we properly export it.

_images/batch-token-export.svg

Direct Token Export

Auric can migrate tokens directly to the target tokenization service via the service’s web API. When the migration is complete, Auric delivers a batch file matching the AuricVault® token ID and the target service’s token ID.

_images/direct-token-migration.svg