Altus allows users to export data from list views to Excel for reporting, analysis, and audit purposes.

While exporting is straightforward, importing data into Altus is more complex and is not supported in a simple, out-of-the-box way without configuration.

Understanding this distinction is important to avoid confusion when working with list data.

Where This Applies

This functionality applies to all list-based entities in Altus, including:

Strategy

• Themes
• Goals
• Benefits

Initiatives

• Portfolios
• Programs
• Projects
• Proposals
• Ideas

Work Regsiters

• Tasks
• Issues
• Dependencies
• Deliverables
• Decisions
• Changes
• Lessons

Resources and Admin

• Resources
• Calendars
• Timesheets
• Confi Settings

👉 Anywhere a list view exists, the same export and import behaviour applies.

Export from a Record (Subgrid View)

Subgrids appear within records such as projects, programs, or portfolios.

Steps

1. Open the relevant record (e.g. Project)
2. Navigate to the register (e.g. Risks, Issues)
3. Select the ellipsis (… ) in the command bar
4. Select Export to Excel

Behaviour

• Only visible columns are exported
• Filters and layout cannot be customised
• Export follows a “what you see is what you get” model

Important:
Subgrid exports may not include all available fields or detailed information.

Export from a Central List (Recommended)

Central lists provide full control for reporting and data extraction.

Steps

1. Navigate to the relevant area (e.g. Work → Risks, Strategy → Benefits)
2. Change the view (e.g. My Active → All Active)
3. Select Edit Filters to refine the dataset
4. Select Edit Columns to include required fields
5. Save the view
6. Select:
7. • Export to Excel, or
   • Use the ellipsis (… )

Why Use the Central List

Central list views allow you to:

• Customise columns
• Apply filters
• Save reusable views
• Export complete and structured datasets

Tip:
Save a customised view before exporting to ensure consistency across reporting cycles.

Importing Data into Altus

Important Limitation

Important:
Although options such as Import from Excel and Import from Template are visible in many areas of Altus, these are not typically usable in a standard out-of-the-box configuration.

• Import functionality requires configuration or automation
• Without this setup, imports may:
• • Fail
  • Appear successful but not correctly map data
  • Create incomplete or orphan records

👉 Always check your organisation’s internal process before attempting imports

Why Import Is Not Straightforward

Altus requires specific system-level identifiers, such as:

• Unique record identifiers (GUIDs)
• Valid system relationships (e.g. Project, Program, Portfolio links)
• Correct field mappings

These identifiers are:

• Often not visible in list views
• Not easily recreated in Excel

👉 This means data imported directly from Excel can:

• Fail validation
• Not link correctly
• Create orphan or unusable records

Excel-Based Editing Considerations

Even when using Excel-based integrations:

• Changes may not map correctly back into Altus
• Hidden system dependencies may prevent updates
• Results can be inconsistent without proper configuration

Tracking Import Progress

When using import methods:

• A “Track Progress” option may appear once during the import process

Important:

• This notification appears only once
• If dismissed, it can be difficult to locate again
• There is no easily accessible or persistent tracking area in standard Altus navigation

Recommended Approach

• ✅ Use Export to Excel for reporting and analysis
• ❌ Avoid using import options unless:
• • A template has been provided
  • The process is defined by your organisation
  • A partner or administrator has configured the functionality

Key Considerations

• Export is simple and reliable
• Import is typically configuration-dependent
• Central list views should be used for reporting
• Subgrid exports are limited
• Data integrity depends on correct system relationships

Tips

• Always export from central lists for full data visibility
• Do not rely on import buttons unless instructed
• Use saved views to standardise reporting
• Consult your administrator or implementation partner for bulk data operations