Project Insight data is managed in a complex SQL Server database structure which cannot be identically replicated outside of the Project Insight application. However, you will find that the data you need to reference following the completion of a project is retrievable within a set of previously saved reports. If you choose to export Project Insight data following the completion of a project, it is important to define the data which is most important and export it in such a way that it can be read with client-based applications.
One common method of exporting project schedule data is to export it to MS Project and save it locally. This will copy the high-level schedule data which maps well between the two applications. It will not capture much of the supporting data which is proprietary to Project Insight such as time entries, comments, issues, approval requests and file uploads to name a few.
The following steps should be reviewed on a regular basis to ensure you are saving the data you need during your data export process:
- Export closed projects to an MS Project or MS Project XML format. Compare the results between the two applications to make sure the scheduling data has translated as expected for long-term local reference
- Practice running reports to retrieve the data you would normally retrieve from a closed project and save those reports. Make it part of the archival routine to run those saved reports and export all of the data into spreadsheets for future reference. Obvious reports might be for time and expense entry, but don't forget to run reports for other information you may find yourself retrieving on a regular basis such as system and user comments
- Download all files which have been uploaded into the project and store the files locally within a folder structure similar to the folder structure within which they are organized in Project Insight
While the above steps will not replicate the complete Project Insight data schema, careful planning and review of the export process can provide for an easy method to retrieve important data long after you have removed it from Project Insight.
The current issue I have with this article is the constraint types that Project Insight uses do not translate to MS Project. I have tried using MS Project 2016. It will not open the extract that comes out of Project Insight.
It's not unusual to have to make adjustments between the two different applications, but the constraints should be the same. Have you identified specific constraints as examples?
It doesn't like ASAP after Task Created Date or ASAP after Project Start.
I see the problem now. Thank you for posting your finding.
We are working on a fix. I discovered in my initial test that "ASAP after Project Start" worked and it was the "ASAP after Task Created Date" that most significantly changed the schedule when imported to Project. I used the bulk edit on the non-summary tasks in PI to change all constraints to "ASAP after Project Start" in a PI project before exporting it. I got the results I expected in my import to Project after that change.
Could you please try this on one of your projects prior to export to see if it works for you? I'll update this thread once we have it fixed.
Thank you Wes. I will give it a try.
I had to export the file out into a formatted Excel. I performed a search and replace of ASAP after Project Start with ASAP. Then I had to bring the file into MS Project 2016. Once I did this I was able to complete what I needed.
Please sign in to leave a comment.