--- title: "Version 3.28 (December 2025)" slug: "dmt-release-notes-3-28" updated: 2026-01-07T11:48:39Z published: 2026-01-07T11:50:25Z canonical: "docs.onespan.com/dmt-release-notes-3-28" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.onespan.com/llms.txt > Use this file to discover all available pages before exploring further. # Version 3.28 (December 2025) ## Deprecated components and features PDF documentation The PDF documentation has been completely removed from the Data Migration Tool product deliverable. You can view the Data Migration Tool user documentation exclusively online on the OneSpan documentation portal, available at [https://docs.onespan.com/sec/docs/data-migration-tool](https://docs.onespan.com/sec/docs/data-migration-tool). Supported platforms, data management systems, and other third-party products Operating systems - Red Hat Enterprise Linux (RHEL) 7, 64-bit - Ubuntu Server 18.04 LTS, 64-bit - Windows Server 2025 ## Known issues Data Migration Tool does not support maker–checker authorization **Description**: Data Migration Tool does not allow data migration if maker–checker authorization is enabled on either the source or the destination system. **Affects**: Data Migration Tool 2.10 and later **Status**: No fix available. Disable maker–checker authorization on both the source and the destination system. Issue 41626: Mobile Authenticator Studio incorrectly set to UNBOUND upon migration **Description**: When you attempt to migrate Mobile Authenticator Studio version 4 that is already present in the destination server, the authenticator becomes UNBOUND upon migration. Issue 20591: User links not migrated upon subsequent migration attempts **Description**: When you migrate data again with the Update Existing Records option enabled, Data Migration Tool may fail to preserve links between linked user accounts. This will occur if: - The user accounts in question were linked after the first migration attempt. - Each linked user account had an assigned authenticator when they were first migrated across. This occurs because Data Migration Tool migrates all user accounts first, and then attempts to re-apply any links between linked user accounts. However, if those user accounts already exist in the destination with assigned authenticator (i.e. as they were when they were first migrated), their links will not be re-applied. **Status**: No fix available. To circumvent this issue, ensure that all user links are applied after the data migration.