Transition from Old Deployment to New Deployment (MFT)

After you have prepared your source and target environments for the migration/side-by-side upgrade, you can transition your production system from old deployment to new deployment.

To transition from old to new deployment:

1. Disable inbound sources in the source environment, if the inbound address in both old and new deployment is same.

   For inbound sources which are remote FTP/SFTP servers, ensure that already processed files in the directory are not processed again after transitioning to the target environment by removing them from the directory.

2. Complete deployment and enable everything in the target environment.

   Note that for some inbound sources, the address is different and clients have to change the address in the source and switch.

3. Switch the DNS.

   The DNS switch is not instantaneous and may take a while (depending on TTL settings in routers) to propagate across the internet.

4. Note that the source environment will continue processing backlogged transfers while new messages are processed by the target environment. When all backlogged transfers are processed and there is no need to rollback, you can destroy the source environment.
   Switch external clients of the embedded FTP and SFTP server that read files to the new deployment, after all files in the old deployment have been processed.
5. If you have directories in the embedded FTP server for storing data that is not processed by MFT, it is up to you to either copy these files or deal with them as you see fit.