If you’re already using Reporting Services and are planning to move your reports to MOSS, you should be aware the migration process is entirely manual. There is no migration utility provided to move your reports to the MOSS server, and you won’t be able to use the RS.exe utility to automate the process of publishing reports to MOSS. Instead, you’ll use the deploy command inDevelopment Studio to copy reports from a Report Server Project to MOSS. Any non-default properties you’ve configured for these reports using Report Manager will be lost because this information is stored only in the native mode report server database and is not contained in the report definition. These properties include report execution options, data sources, parameters, and subscription settings. You must reconfigure these properties using each report’s context menu in MOSS. I’ll detail the steps to deploy reports and to configure properties in the second article in this series. Lastly, if you’re been accumulating report history, you should plan to export the history to another format, such as PDF or Excel, and then upload to a SharePoint library. There isn’t a way to automatically connect these exported copies of report history to the source report in MOSS, but at least the history can still be accessible to the user community.