So you've decided that a mainframe migration is just the thing to save your organisation money and time. But the key is, as Malcolm Marais puts it, to do it right. Performing the migration successfully take some consideration and technique, as explained in the 10 items Marias includes in this article. The first item is to ensure that components of the migration are all designed and assigned clear ownership – these include primary development language, infrastructure, output, and disaster recovery. He also includes that “organizing support processes and operations environment support during the project phase” is key: Address internal support processes and other operational considerations during project planning and solution design to assist in developing a realistic delivery schedule and minimize rework or unexpected delays. The application team running a project frequently lacks experience with infrastructure projects and related procurement/support processes in the target environment. It is important for the delivery team(s) to understand the internal processes, lead times, change windows, lockdown schedules, and other constraints. Another tip is to make sure that a specific plan exists for cost savings, and that those savings are tracked and achievements recorded. The return on investment is a key factor in determining whether the migration is achieving one of its primary purposes: saving your organisation money!