Hello, I am in the process of creating a MOSS 2007 site for a client that tracks and displays a complex set of data. To accomplish this the site has a number of lists, each containing different custom content types and columns (including lookup and calculated columns). The 'dashboard' is simply a set of webpart views, although a customized Gantt chart has been created using javascript/jQuery in a CEWP. The problem: Due to time/technical constraints I am forced to develop this site in my company's sharepoint environment, with the expectation of redeploying the finished product in the client environment. Is it possible, and what would I have to do to preserve the functionality of the site/lists? Ideally, I would like to package the entire site as is, but my understanding is that saving a site as a template (.stp) does not keep custom columns/content types. Would I have to create a custom site definition? Create a custom feature? Unfortunately this is a bit out of my experience with MOSS 2007. Any advice or instructions in the matter would be massively appreciated. Thanks!

1st option you can create a new webapplication and site collection in the client place and restore with your database which was created at your company. 2nd option Save it as a "Site Template" and restore it in client place. there are 2 options to create sitecolumns and sitecontent types Use Powershell script or write a feature to create sitecolumns and sitecontent types 3rd option you can go for site and list definitions however it takes so much of time to develop and little bit complex. Surya.P

Sounds like you are deep into the implementation phase and have already defined the entire taxonomy with data using the SharePoint GUI. Backup restore At this point the simplest solution is to do a site collection export and import (here you can choose to exclude any security information so that your test environment users do not get provisioned in production)You can do a full content database backup and restore to your production. In this case you would have the manual work of going in and cleaning up the test environment users. Not too bad, probably a c# console app or a Powershell script will do the job. Content Migration A third option would be look into content migration using a third party tool, for e.g. perform a search for "SharePoint content migration" in a search engine. The restriction with this method is that both the test and production environment must be accessible at the same time. Some of them do offer saving to file and then importing from it, however, in my personal experience this has not worked too well.And you have the SharePoint content deployment. Generally I have not had the best experience with this, so tread carefully with this method. http://blogs.msdn.com/b/jackiebo/archive/2007/02/26/content-deployment-step-by-step-tutorial.aspx Trying to create features at this point is out of the question since you are very well into your site structure setup and without incrementally testing your feature build out chances of failure is high. Hope this helps Anand