Migrate jobs from Compliance Engines to DCT

Use this task to migrate existing Compliance Engine jobs to DCT interface. After migration, you can manage the jobs by using DCT role-based access control, tags, and policies.

Before you migrate jobs, if the source Compliance Engine is already connected in DCT, open Data > Data Infrastructure > Data Engines, click View for the engine, and convert it to a migration engine from the engine details page. For more information about opening the details page, see Engine details page. Alternatively, connect a new engine as a migration engine by selecting Continuous Compliance (Migrate Assets) in the Connect Engine wizard.

Prerequisites

  • The source Compliance Engine is connected as a migration engine in DCT and runs version 2026.5 or later.

  • A Job Orchestrator is registered in DCT.

  • You have the ENGINE READ and ENGINE MIGRATE_COMPLIANCE_JOBS permissions.

Migrate jobs

  1. Open the details page for the source Compliance Engine and go to the Available Assets tab.

  2. Select the jobs to migrate. You can migrate Masking, Tokenization, and Re-identification jobs.

    Profile jobs are not eligible for migration.

  3. Click Migrate Jobs.

  4. Configure the migration options. Choose one of the following modes:

    • Align with DCT reuses existing DCT built-in data classes and algorithms and adds only missing objects.

    • Preserve Engine State creates a fresh instance of every object and preserves the engine configuration. Algorithm keys are preserved, so masking results are the same when you run the job from DCT.

    Click Next.

  5. In the Summary step, review the migration configuration, and then click Submit.

DCT creates a MASKING_JOB_MIGRATE job for the migration. The source-engine jobs are not deleted or modified.

Monitor a migration

Monitor the MASKING_JOB_MIGRATE job from Administration > Operations. For more information, see Operations in DCT. When the job completes, download the PDF or CSV migration report from the job details. Reports are available for 180 days after job completion.

Realign a migrated rule set

Only rule sets migrated with Preserve Engine State can be realigned. To replace migrated algorithm and data class copies with DCT built-in objects, open the migrated rule set and click Align to DCT Standard. You can realign a rule set only once within 30 days of migration.

Synchronize mapping data

For imported Mapping algorithms, review the mappings_status value. A status of NOT_SYNCED means the algorithm is present in DCT but its mapping data is not available. When needed, synchronize mapping data from the algorithm details page or by using the Sync object mappings rule set action.

Do not delete an imported Mapping algorithm or deregister its source engine while mapping synchronization is in progress. DCT blocks these operations while the status is SYNCING.

Limitations

  • Each migration request can include from 1 through 100 jobs from one source Compliance Engine.

  • Connector credentials are not migrated to DCT for security reasons. After migration, update the connector credentials in DCT.

  • A completed migration cannot be undone.

  • Remote Mapping algorithms require credential completion and cannot synchronize mapping data by using the synchronization endpoint.

Use the API

Use GET /v3/migratable-jobs or POST /v3/migratable-jobs/search to find jobs that can be migrated. To migrate jobs, use POST /v3/migratable-jobs/migrate. See API references for API documentation.