Software companies today often face the necessity to decide where to develop their products. Inability to employ people or continue ongoing development with the same capacity in a given site of a company often leads to relocation of software work from one site to another. Software product transfers, however, are associated with numerous challenges that require investments, and may also have a secondary harder to capture effect on development productivity, quality and scope. In this paper, we share the results from previous empirical studies of software product transfers and offer a checklist for risk identification. The checklist shall be useful for software companies that consider, plan or execute software transfers. Although many risk factors included in the checklist may seem obvious, our empirical observations indicate that prior to obtaining the necessary experience these factors have been initially overlooked. Thus we believe that the checklist will be especially useful for managers with no or little experiences in relocating software work between the two sites of the same company.