> 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-3.0-2026/automated-p6-ready-xls-export-for-actuals.md). # Automated P6-Ready XLS Export for Actuals On large construction projects, the master schedule lives in Primavera P6, but day-to-day progress tracking happens in VisiLean. Every reporting cycle, getting actuals back into P6 is a multi-step manual process. #### Why This Matters Schedule updates between VisiLean and Primavera P6 are a contractual necessity on most large-scale projects. Clients, PMCs, and joint venture partners expect the P6 master programme to reflect current reality and they expect it updated regularly. When that update cycle depends on manual data wrangling, it creates a bottleneck that doesn't scale. Planners spend hours on formatting instead of analysis, updates get delayed, and every manual touchpoint introduces the risk of transcription errors reaching the master schedule. For enterprise customers running hundreds of projects, this has been a deployment blocker. #### What's New? * **One-click XLS export of actuals**: Export actual progress data from VisiLean in P6's native spreadsheet import format, targeting the Activities subject area. The file is ready to import via P6's File → Import → Spreadsheet (XLS) workflow with no manual field mapping. * **P6 XLS format, not XML or .xer:** The export uses P6's spreadsheet import format by design, sidestepping the calendar, granularity, and duration logic issues that made the previous MPXJ-based approach unreliable. * **Activities subject area only:** The export covers actuals-related activity fields (Activity ID, Actual Start, Actual Finish, % Complete, and related columns). Resource assignments, expenses, and predecessor/successor relationships are out of scope for this release. #### How It Helps A *Planner* managing a 3,000-activity infrastructure programme collects weekly actuals in VisiLean, downloads the P6-ready XLS file, and imports it into Primavera in minutes. A *Project Controls Manager* on a joint venture project needs to submit updated actuals to the client's PMC every fortnight. Instead of going through a lot of manual steps, they generate the export directly, verify it against the progress report, and submit it with confidence that P6's import validation will accept it on the first attempt. A *Senior Planner* overseeing an enterprise rollout across hundreds of projects exports actuals from each project in sequence, imports them into the corresponding P6 files, and produces a consolidated portfolio-level schedule update within a single afternoon - a process that previously required dedicated support involvement per project. #### Key Considerations & Caution Points **Activities subject area only.** This release covers activity-level actuals (Actual Start, Actual Finish, % Complete). Resource assignments, expenses, and relationship (predecessor/successor) exports are not included and remain on the roadmap. **Day-level granularity.** VisiLean continues to operate at day-level precision. The exported XLS reflects this hourly precision fields in P6 will show day-level values. **Existing MPXJ export unchanged.** This new export sits alongside the existing P6 file export. The previous mechanism is not modified or removed. **Available for only .xer file imports.** This functionality is available only for .xer type of file --- # 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-3.0-2026/automated-p6-ready-xls-export-for-actuals.md?ask=&goal= ``` `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.