> For the complete documentation index, see [llms.txt](https://changelog.visilean.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://changelog.visilean.com/changelog/release-1.0-2025/enhanced-microsoft-project-export-and-update-in-visilean.md).

# Enhanced Microsoft Project Export & Update in VisiLean

Managing construction schedules has never been more reliable! We are excited to introduce a powerful enhancement to VisiLean’s integration with Microsoft Project (MSP), ensuring accurate project updates with improved data consistency.

With this update, you can now choose between VisiLean Unique IDs or MSP Unique IDs when updating schedules, maintaining full data integrity. One of the biggest challenges in working with MSP has been its inconsistent ID handling, which often results in mismatched updates and data loss. Our latest enhancement addresses this by introducing a structured approach using GUIDs within VisiLean, providing a stable reference for all updates.

### **Key Benefits**

* **Improved Data Alignment:** Maintain consistency across updates with an advanced ID mapping system.
* **Flexible Update Options:** Choose between GUID-based updates or External ID mapping based on project requirements.
* **Stronger Data Integrity:** Eliminate workflow disruptions and mismatches when exporting and updating schedules.
* **Enhanced Compatibility:** XML-based export ensures smooth data handling between VisiLean and MSP.

This update enhances project tracking, reduces errors, and increases confidence in your schedules. By maintaining a structured mapping of IDs, it minimises confusion and ensures that updates accurately reflect the true state of your projects.

We are confident that this improvement will provide immense value to teams relying on MSP for scheduling while executing in VisiLean. Try it today and experience greater control over your project updates!

{% hint style="info" %}

### **Key Considerations & Caution Points**

* When importing via VisiLean Unique IDs, always follow the proper workflow to ensure that VisiLean GUIDs are present in the incoming schedule during updates. This prevents duplication of activities.
* Ensure XML files exported from VisiLean retain GUID integrity before re-importing into MSP to maintain accurate activity mapping.
* MSP may generate new Unique IDs upon updates, so using GUIDs within VisiLean is strongly recommended for maintaining data accuracy.
* Double-check that all updated schedules are mapped correctly before importing back into VisiLean to avoid data misalignment.
  {% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://changelog.visilean.com/changelog/release-1.0-2025/enhanced-microsoft-project-export-and-update-in-visilean.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.