English
Unable to Migrate to the New eZsign Version 4+
If you see a message indicating that your migration to the new version of eZsign (version 4+) cannot be completed, it means that one or more conditions are temporarily blocking the process.
Below are the possible scenarios and the corresponding solutions.
- Conditions Preventing Migration
- Case 1 - Incompatible Files :
**Message in the application -**Your migration cannot be completed at this time.
You have one (1) signing file containing elements that are not compatible with the new eZsign interface.
You will be able to migrate your account once these signatures are completed or the related files have been archived.
These files will be eligible for archiving as of November 3rd, 2025.
Explanation - A file currently in the signing process contains a field that no longer exists in the new eZsign.
The Accepted / refused / CP field will no longer be used in the new version.
The process for adding a response on an OACIQ form has been redesigned and will now be done using an annotation in the new eZsign.
For this reason, your eZsign account cannot be migrated if a file containing these fields is still in progress.
Solution - Wait until all signatures have been completed, then archive the affected files. Once the archiving is complete, you will be able to restart the migration.
Note : To learn how to add a response on an OACIQ form using the new eZsign, please refer to this article.
- Case 2 - User Belonging to a Group with Shared Files
**Message in the application -**Your migration cannot be completed at this time.
You are part of a user group that shares common file types. All members of this group must be migrated simultaneously.
Please contact your administrator so they can request a group migration from eZmax.
You may also wait for the automatic migration , which will occur on the scheduled date for all accounts.
Explanation - You belong to a group of users with shared eZsign files.
In this case, all users in the group must be migrated simultaneously, and this process must be handled by the eZmax team.
Solution - Your administrator must submit a support ticket indicating that some users cannot be migrated because they are part of a group sharing eZsign files.
You can also wait for the automatic migration , which will occur on the scheduled date for all accounts.
Example of a support ticket :
Subject : CLIENT CODE - Migration of a User Group
Message : Please migrate the following user group:
– First name and last name + username of each group member
- Case 3 - Incompatible eZmax Version
**Message in the application -**Your migration cannot be completed at this time.
The new eZsign interface is not compatible with the older version of the eZmax application.
To proceed with the migration, please install and use the new (4+) version of eZmax by clicking here, then restart the process.
It willno longer be possible to access the old eZsign** , regardless of the situation, if the update to version 4+ has not been completed before December 18th, 2025.**
Explanation - The old version of eZmax does not include — and will never include — the new eZsign.
You therefore cannot use the new eZsign while still using the old application.
Solution - Install and use the version 4+ of eZmax (click here to download), then restart the migration process.
Warning
Access to the old eZsign will no longer be available, regardless of the situation, if the update to version 4+ has not been completed by December 18, 2025.
- Migration Possible, but with Files to Archive
Your migration can be completed, but some files will need to be automatically archived before the transfer.
Message in the application - Migration possible, but with files to be archived
Before proceeding with the migration , please note that two (2) files will be automatically archived , as they contain elements no longer compatible with the new version of eZsign.
Once the archiving is complete, you can finalize your migration without issue.
Explanation - Some files contain a field that no longer exists in the new eZsign (the Accepted / Refused / CP field).
The process for responding to an OACIQ form has been redesigned and is now done using an annotation.
That is why your migration can only be completed if these files are at the Archived stage (and not at the Completed stage).
Solution - These files will be automatically archived before migration.
Once this step is complete, the migration will proceed normally.
You will not lose any signatures from these files — they will simply be moved to the Archived stage.