Set up and maintain sync with external execution tools
The External Execution Tools configuration allows organisations to integrate Altus with external scheduling and execution tools (e.g. Microsoft Project, Planner, Azure DevOps, Jira).
Altus supports synchronisation of project-level data and metadata with external systems, enabling visibility and alignment across delivery tools.
Altus is scheduling tool-agnostic, allowing organisations to select the most appropriate execution tool for different project types. [docs.altus.pro]
Important: Permissions Required
This task is available to users with administrative access to Settings in Altus.
- If you do not see the required options, you may not have sufficient permissions
- Contact your system administrator or Altus Partner for support
Accessing External Execution Tools
- Navigate to Settings
- Locate the Project Sync section
- Select External Systems
This area displays all configured external execution tool connections.
Understanding External Execution Tool Configuration
Each external system configuration defines how Altus connects to and synchronises with an external tool.
Key elements include:
- External System Record – Identifies the tool (e.g. Microsoft Project, Planner)
- Project Sync Entity – Defines the data structure used for sync
- Dataflows – Handle data ingestion from external systems
- Metadata Mapping – Controls how fields align between Altus and the external system
External execution tool synchronisation relies on Power Platform Dataflows and supporting configuration components. [docs.altus.pro]
Creating a New External System Connection
To configure a new external execution tool:
- Select New
- Enter required details:
- Name – External system name
- Project Sync Entity Name – Associated sync entity
- Configure any required integration or connection settings
- Select Save or Save & Close
Initial setup may require configuration of dataflows and mappings depending on the tool being integrated.
Updating an Existing Connection
To update or adjust an existing external system sync:
- Select the External System record
- Review and update configuration as required
- Select Save or Save & Close
Important: Updating Connection Behaviour
Changes to an external execution tool connection may require updates beyond the External System record.
Depending on the scenario, updates may involve:
- Dataflows (to adjust data ingestion or refresh logic)
- Dataverse tables (supporting sync structures)
- Metadata mappings (field alignment between systems)
- Plugin steps or sync logic
Some changes may only require minor updates, while others may require modification across multiple integration components.
For more advanced changes, support from an Altus Partner or technical resource is typically required.
How Synchronisation Works
- Data is pulled from external systems using scheduled dataflows
- Data is stored in supporting entities within Altus
- Plugins and sync logic process and align data between systems
- Projects can be linked to external records to enable synchronisation
External tools often act as the source of truth for execution data.
Important Considerations
- Not all data is editable in Altus — some fields may be read-only when synced
- External systems may be the authoritative source for task and schedule updates
- Sync behaviour depends on configuration and integration design
- Organisations can configure multiple external tool connections
How to Use This Feature
Use External Execution Tool sync to:
- Integrate Altus with project delivery tools
- Maintain a single view of portfolio and execution data
- Support hybrid delivery models (Altus + external tools)
- Enable consistent reporting across systems
Tips
- Define a clear source of truth for project data
- Use standard dataflow templates where available
- Test configuration changes before enabling for active projects
- Monitor sync behaviour and logs for alignment issues
- See https://docs.altus.pro/products/AltusPPM/AsBuilt/Overview/External-Execution-Tools.html for more information.