We utilise the Now-Next-Later format to express our current and future work on Archivematica and its dependencies. This allows us to communicate our work openly, while maintaining flexibility and the ability to make new discoveries to support the project. Rather than being time bound, we acknowledge the complexity of software development and the need to be innovative and product led.

The Now category acknowledges the release and other high priority work we are currently undertaking. This work is viable and clearly defined. Some of this work might be project-related, but not for the next release. We use milestones to group issues together for the current release. Viewing a milestone will give you all the issues being addressed, even if they are not expressed in this roadmap. Milestones will always have the most up-to-date release information. If an issue is not tagged to a milestone then it is not going to be included in the release.

The Next section of the roadmap articulates the upcoming problems being scoped and is always dependent on the outcomes of current work. This can include reprioritised work. There is always space to add to it as we move it to the Now category.

The Later work characterises our long-term goals for Archivematica. They are things we would like to tackle, but the research to better understand the problem has not been done. Sometimes the work in Later is broad in scope, ready to be broken into smaller, viable tasks. There is no time limit to things residing in the Later category.

Updated: 18 December 2025

• 1.19 release - view milestone
  • Address slow store_aip tasks when replicating to a large BackBlaze bucket with rclone - community contribution, Storage Service
  • Fix dashboard timeouts in S3 Transfer Sources with 100k+ objects
  • Remove Python 3.9
  • Delete AIP via API
  • Django upgrade to 5.2
  • Replace pip with uv
  • Upgrade to MySQL 8.4
  • Drop Angular 1.x and upgrade jQuery library
  • Transfer browser improvements

• 1.20 release planning - milestone pending
• Elasticsearch upgrade to 9.x
• Django upgrade to 6.2
• Extend API coverage
• Tools extension API
• Preservation planning API
• AIP versioning investigations and design
• Pagination for transfer and ingest tabs
• Ability to download normalization reports

• Simplify PRONOM updates
• Improve process for tool updating
• Remove externals
• Investigate simplifying UI (E.g. More intuitive preservation planning tab)
• Remove need for multiple pipelines
• Extend options for user permissions
• Improve error reporting
• Model Intellectual Entities in AIP metadata
• Investigate extended functionality and performance
  • Running Fixity from the UI
  • Moving and migrating AIPs
  • DIP on demand
  • AIP creation reports
  • Extend Stored AIP reporting