---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Migrate from Edge Encryption to Field Encryption

# Migrate from Edge Encryption to Field Encryption {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Migrate from Edge Encryption to Field Encryption to take advantage of the latest security features.

## Migration process {#migrate-ee-to-fe__prereq_lbz_ghx_ldc}

This topic covers, which comprise the following steps:

1. Migrate columns and attachment from Edge Encryption to Field Encryption.
2. Stop and disabling Edge Encryption proxy servers.
3. De-tokenize your data
4. Decrypt Service Catalog item variables.
{#migrate-ee-to-fe__ol_vnl_m3x_ldc}

## Limitations {#migrate-ee-to-fe__section_jkn_3kx_ldc}

* Field Encryption doesn't currently support tokenizing data in the same way that Edge Encryption does. Data that is tokenized through Edge Encryption must be included in an encrypted field configuration for Field Encryption.
* Field Encryption doesn't currently support encrypting Service Catalog item variables.
{#migrate-ee-to-fe__ul_wzm_jkx_ldc}
* **[Configure Field Encryption for your Edge Encrypted fields](https://servicenow-prod.fluidtopics.net/mh0gcTQRgnPwxPrUwcSD3Q)**   
  Before migrating your existing edge encrypted fields to Field Encryption, you must configure field encryption for these fields.

