What is the upgrade policy?
Transend Migrator and Transend Migrator Forensic Edition come with 30 days of free technical support; and during this time, any new versions are free. The purchase of Annual Support extends free upgrades to one year from date of purchase. Please be sure to obtain the latest version prior to the expiration of your free maintenance period.
If you download the current software and your old license key does not work with the new version, AND if you are within the maintenance period, please email your license key (name, organization, and key value) to us; we will confirm your status and issue a new key. If you have an older license and have misplaced your software, please contact us.
If you are not within the maintenance period and wish to upgrade, pricing is as follows: 50% of the the current license price. We will confirm the original sale and provide payment options. Upgrading provides an additional 30 days of technical support, including new versions available during the period.
What is the refund policy?
All Transend products are available for download on a try-before-you-buy basis. We provide a free trial of the software to let you fully evaluate our products before making a purchase decision. During your trial period, and after you’ve purchased the software, our support staff is available to assist with installation and configuration via email or telephone. We strongly recommend that all customers download, install, and test the trial version of any product prior to making a purchase.
In certain instances, if due to technical difficulties or platform incompatibilities the software will not function properly, we may, at our discretion, issue a refund. In such instances, we require that you have contacted (and received) technical support to ensure you have taken all necessary steps to correctly operate the software prior to being eligible for a refund.
What are the system requirements?
The following hardware and software are the minimum requirements to use Transend Migrator.
- Pentium III or higher
- 16MB of RAM (512MB or greater is recommended)
- Windows XP, Vista, or Windows 7
- 40MB of available hard disk space and enough space to store migrated files
- Internet connection required for license verification
- Windows 7 Professional with current service packs
- Pentium 4, 3.0GHz system or greater
- 4GB RAM or greater (optimized for your motherboard)
- 7200 RPM or faster hard drive
- 50% or more free space on hard drive and enough space to store data files
- High performance 10/100/1000 network adapter
- Independent video card (does not borrow from system RAM)
What if I do not have internet access?
Internet access is required for license validation. If you absolutely cannot run the software on a machine with internet access, please contact us.
What if my network uses a proxy server?
If your network uses a proxy server then you may need to use the /PROXY switch found in the General section of Custom Options (under the Migration Options menu). Enable the /Proxy switch and Transend Migrator will attempt to retrieve your proxy settings for license key validation. More proxy information can be found in the help file under Installation > Proxy.
Note: If you use the /PROXY switch but you still have problems connecting to the licensing server, look inside the Transend Migrator log file directory for a file called response.html. Open up the file and review the contents. This file will be created when there is a failure connecting to the proxy server, and it is useful in troubleshooting the connection.
What if my network is behind a firewall?
Ensure your firewall allows access to the following two web sites. Otherwise, your license key verification may not work:
What if my messaging system isn’t listed in the Supported Email Types?
If your particular message system or file type is not listed in Supported Email Types, please contact us to verify if we can support it. There are many systems that we don’t list by name but do support because they are supported through a standard format.
Is it required that I have Outlook installed to migrate to or from Exchange or a PST?
Transend Migrator requires that 32bit Outlook is installed on the computer where Transend Migrator is installed. When converting Microsoft Exchange, Transend Migrator will use the Outlook API and usually MAPI to connect to the Exchange Server. However, Microsoft Outlook is not required in order to convert from an OST or PST file when using OST/PST (non-MAPI) mode.
When migrating into Exchange, does the account I use need to be a member of Active Directory?
The account you use to perform a migration must be an active member of the domain you are converting from or to. This AD account must have, at a minimum, receive-as permissions on the Exchange Information Store or Mailbox Database.
How can I ensure that my account has the necessary security permissions to perform a batch migration?
We recommend that you attempt to access multiple Exchange Accounts using the Outlook email client to ensure the account performing the migration has the proper security permissions applied. To perform this test, log into Windows using an AD account who is a member of the Migration group or who has been given the above permissions. Then, go into the control panel, select the Mail icon, and create a new profile for a user other than the current logged on user.
Start Outlook (you might want Outlook to prompt for profiles). Select the test account and verify that you can log into that account directly without being prompted for a password. If you are not prompted for a password then the permissions have been set. You can now continue migrating to multiple users.
If you are still prompted for a password, then it is possible that you have multiple Windows Servers, who have Active Directory, and you may need to wait at least 20 minutes. Otherwise, verify that your account has the proper permissions, and test again.
Lotus Domino / Notes
What are the basic requirements when migrating to or from Lotus Domino/Notes?
Transend Migrator can migrate Lotus Notes email data whether or not the Lotus mail file is stored on the local workstation or if the Notes account is on a Domino message server.
The Lotus Notes email client version 5.x or above is required. If the NSF file is protected, the ID file, account name, and password will be required to access the NSF file. If the NSF file is accessed via a live Domino server then you will need the account information in order to access it. If the NSF file is taken from the Domino server and placed onto the local workstation you can bypass the need for an ID file. Normally, the NSF file is only protected when it is accessed through a Domino server or if the user elects to protect the file. Lastly, if messages are encrypted, then the ID file and password is required.
Is the Lotus Notes client required to migrate to or from Domino/Notes?
The Lotus Notes email client is required, and must be fully installed on the computer performing the migration.
The Lotus Notes software should be installed into its default location, and setup as a stand-alone client (if you do not need to use an ID file and password). If connecting to a Domino Server then set it up as an active client and provide the ID file and password for the account you are migrating.
Under normal circumstances, Notes will prompt the user with a password dialog whenever a database or account is opened. Transend Migrator will intercept this prompt and supply the password you typed into the password box. In order for this interception to work, you must add one of the following statements into your notes.ini file. The Notes.ini file should be located inside the Notes installation directory.
extmgr_addins=tmnts.dll (for Notes versions prior to version 6)
You may also bypass the password prompt by entering the password and ID file path and filename into the Transend Migrator password text box.
If I don’t have a Notes client, how can I obtain one for free?
You can download a free trial of Lotus Notes from the IBM website and this will satisfy the requirement of having a Notes client installed for migration purposes.
Is the GroupWise client required to migrate to or from Novell GroupWise?
The GroupWise client software is required when using the GroupWise API. The IMAP4 protocol must be enabled on the GroupWise server if using the IMAP4 method. Lastly, an active or live GroupWise email account must exist. The logon and password is required. Optionally, you can migrate another account if you have proxy access to that account or by using Trusted Mode.
How do I batch migrate from or to GroupWise without needing each user’s password?
Normally, you will use a logon and password in order to connect to the GroupWise email server. If you will be migrating multiple GroupWise accounts you may use Trusted or Proxy access. Trusted Access allows you to perform migrations for users without having to know each user’s password. You must have admin permission on the GroupWise server in order to use Trusted Access. A user ID is still required, and you must be running GroupWise 6.5 or greater for this ability to be used. Proxy access does not require admin permission. Instead, the alternate user account you will be migrating must give you proxy access to their data.
Is my version of GroupWise stable enough to perform a migration?
Ensure you are running a stable release of GroupWise, and use the recommended patches or updates required by Novell. If you are running GroupWise versions 6 then patch to version 6.5.7. If you are running version 7 then patch to 7.0.3 or greater. Similarly, if you are running GroupWise version 8 then patch to version 8.0.1 or greater.
How do I get around the GroupWise/Outlook MAPI conflict?
If you are migrating email between GroupWise and Microsoft Outlook, the recommended email migration method is via the IMAP protocol. This is because GroupWise and Outlook both use a program file called MAPI32.DLL, and both email programs use their own versions. Because of this, you may not be able to convert email directly between GroupWise and Outlook. Therefore, we recommend you use the IMAP migration choices when it is possible.
If the IMAP4 protocol is not available, and if you are getting connection problems between GroupWise and Outlook, then consider performing a 2-step migration. A 2-step migration means that you convert to a mail format other than GroupWise or Outlook and then convert from that format type to your destination application. For example, you may want to convert GroupWise messages into a Transport File, and then convert the Transport File into Microsoft Outlook/Exchange.