How to Update or Upgrade EdbMails Office 365 Migration Software
Use this guide to update an existing EdbMails Office 365 Migration Tool installation to the latest available build. The update should be planned around active migration work: record the current status, pause at a suitable point, install the new build on each migration computer, and verify the application before resuming.
The current EdbMails policy for this product allows licensed users to install available version upgrades without a separate major-version upgrade charge. If the application displays an activation or entitlement message, confirm the license status with EdbMails support before continuing.
Before Updating EdbMails
| Condition | Correct route | Why |
|---|---|---|
| A migration operation is running | Allow the current activity to reach a suitable stopping point, then record the status and pause it | The installer closes EdbMails and a paused operation must be resumed manually after the update. |
| EdbMails is installed on several computers | Plan the update for every migration computer | Keeping the same approved build across the project makes behavior and troubleshooting easier to compare. |
| You need further incremental or retry passes | Keep the same computer, project information, source, target, and mappings available | Subsequent passes depend on the retained migration context; verify reports before resuming. |
| The Windows environment or security policy changed | Review the current system requirements and allow the signed installer under your organization’s policy | An operating-system, permission, endpoint-protection, or network restriction can interrupt installation. |
| You are moving EdbMails to another computer | Contact support or follow the applicable migration-computer procedure instead of treating it as an in-place update | A new computer may not contain the local project state used by the existing installation. |
Understand the EdbMails Version Number
The installed version appears near the top of the main EdbMails window. It uses four dot-separated values, for example: 6.1.1.10.
Format: [major].[minor].[maintenance].[build]
- Major: Identifies a substantial product release and changes less frequently.
- Minor: Identifies a planned release that may include features or product improvements.
- Maintenance: Identifies a maintenance release, commonly used for targeted fixes.
- Build: Identifies a specific compiled build and may change for smaller fixes or refinements.
The in-place procedure below applies when installing a newer supported EdbMails build on the computer where the application is already installed. Review the release notes when any part of the version changes.
Steps to Update or Upgrade EdbMails
- Review the current release notes and confirm that the migration computer meets the published system requirements.
- Record the installed version, active batch status, source and target connections, mappings, and recent report location.
- Pause active migration work at a suitable point. Do not start the installer while you are relying on an unattended operation to continue.
- Use the official download button in the resources section to obtain the current EdbMails installer.
- Run the installer on the same computer where EdbMails is installed. The application closes when the installer begins, and a running migration is paused.
- If the project uses EdbMails on more than one computer, repeat the update on each one before continuing its assigned batches.
- Open EdbMails after installation, confirm the displayed version, and verify the expected configuration before manually resuming paused work.
Validate the Application After the Update
- Confirm that the expected new version appears in the main application window.
- Check that the source and target connection entries belong to the intended migration project.
- Review mailbox lists, mappings, filters, and the last migration report before continuing.
- Confirm that previously paused jobs remain paused until you intentionally restart them.
- Resume a small batch or pilot first when the update occurs during an active project, then review the resulting report.
Troubleshoot an EdbMails Update
| Condition | Correct route | Why |
|---|---|---|
| The installer does not start or is blocked | Check Windows permissions, application-control policy, endpoint protection, and the installer source | The migration application cannot be updated until the Windows installation is permitted. |
| The old version still appears | Close all EdbMails processes, rerun the current installer, and verify which executable or shortcut is being opened | An older process or shortcut can make it appear that the update was not applied. |
| Connections, settings, or jobs are not as expected | Do not recreate or overwrite the project immediately; compare the computer, Windows profile, version, and saved reports, then contact support | Opening a different local context can look like lost configuration and may complicate recovery. |
| The application requests activation | Verify the license details and contact EdbMails support if the activation state does not carry forward | Licensing or machine-specific changes may require review before migration continues. |
| The migration remains paused | Review the job, mapping, and report, then resume it manually | The installer does not automatically restart paused migration work. |
| Different computers show different versions | Update each migration computer to the approved build used for the project | Consistent versions simplify validation and support diagnostics across parallel batches. |
Complete the Update
An application update does not replace migration validation. After resuming work, monitor the next batch and review its report before continuing with the remaining mailboxes. Retain the pre-update and post-update version details with the project records so support can identify the environment if a later issue needs investigation.
Frequently Asked Questions
What is the difference between an EdbMails update and an upgrade?
What happens if a migration is running when I update EdbMails?
Are my settings and migration jobs preserved during an update?
Will I need to activate EdbMails again after upgrading?
Do I need to update EdbMails on every migration computer?
