Soon you'll receive an invitation to upgrade your Symantec, GeoTrust, Thawte, or RapidSSL console to DigiCert® CertCentral. When you active your new account, some data from your existing account is automatically migrated over, some data you must migrate yourself, and some data
e you must manually add to your new account.
When we migrate data from your existing account, we aren't removing it from your account. Rather, we are copying the information from your existing account and adding it to your new CertCentral account. In other words, data migration takes data from your old account and syncs it with your CertCentral account.
Data migration only works one way: old account to CertCentral. We don't migrate data from your CertCentral account to your old account.
For example, when you add a new organization in your old account, we sync it to your CertCentral account. Once the organization is validated, we automatically migrate the organization to your CertCentral account.When you add a new organization in your CertCentral account, we don't sync it to your old account, and we never migrate the validated organization to your old account.
As of February 12, 2020, when you activate your new CertCentral account, you should be aware what data is migrated automatically, what data you can migrate yourself, and what data you'll need to manually add yourself.
As of June 2019, in preparation for your upgrade to CertCentral, we've been automatically migrating your validated organizations over from your current console to your CertCentral account. Each time you added a new validated organization to your old account, we added that organization to your CertCentral account.
As of February 12, 2020, validated organization validation (OV) and extended validation (EV) domains are migrated when you activate your DigiCert® CertCentral account.
Certificates are not automatically migrated to your newly activated CertCentral account. However, you can import certificates yourself. As of February 12, 2020, only active public SSL/TLS certificates can be imported.
De-activated SSL/TLS certificates cannot be migrated from your legacy account. At this time, only active public SSL/TLS certificates can be imported.
Pending SSL/TLS certificates
Pending public SSL/TLS certificates cannot be imported. However, importing certificates is not a one-time process. After public DV, OV, and EV SSL/TLS are issued, import them any time.
Previous CWS discovery scan results are not transferred to CertCentral Discovery. However, you can repoint existing sensors to communicate with CertCentral Discovery. You can also move your sensor and scan settings from CWS discovery over to CertCentral Discovery.
CertCentral Discovery will be ready to scan your network again immediately following the sensor and scan transfer! Then, run one-time scans or wait for scheduled scans to bring new certificate discovery data into CertCentral Discovery.
Private SSL/TLS, code signing, S/Mime and other types of certificates cannot be migrated at this time. Non-SSL/TLS certificate will be part of a separate migration effort.
Account contacts, such as administrators, subscribers, and other users, are not transferred to your new CertCentral account. You must manually add them to your CertCentral account yourself.
See Manage users.