Avion Knowledge Base
avion.ioSign inSign up
  • 👋Introduction
  • 👉Getting started
    • What is Avion?
    • Define your product backbone
    • Scoping and prioritizing your product
    • Creating your release plan
    • Aligning the team
    • Integrating with backlog tools
  • Docs
    • 👏Core concepts
      • Projects
        • Project team
        • Migrating to projects
      • Organizations
        • Invite a member
        • Remove a member
        • Roles
        • Transfer ownership
        • Configure your path
        • Delete your organization
    • 🚀Story map
      • Story map anatomy
      • Journeys and steps
      • Stories
      • Releases
      • Attachments
      • Tags
      • Personas
      • Labels
      • Dependencies
      • Search and filter
      • Sharing
        • Restricted links
        • Public links
      • Workflow
      • Importing data
        • Import from Excel
          • XLSX import template
        • Import from StoriesOnBoard
      • Exporting data
        • Export to PDF
        • Export to image
        • Export to CSV
        • Export to Excel
      • Rich text editor
        • Keyboard shortcuts
        • Known limitations
      • Keyboard shortcuts
      • Tips
    • 🤝Integrations
      • Backlog tools
        • Set up an integration
          • Authentication
          • Project / board selection
          • Backbone syncing
          • Map story states
          • Additional syncing options
          • Importing data
        • Sync data
          • Pushing
          • Importing
          • Attachments
          • Deleting data
        • Configuration
        • Pause an integration
        • Re-authenticate
        • Remove an integration
        • Maintenance
          • Removing stale webhooks
        • FAQs and troubleshooting
        • Services
          • Jira Cloud
            • Features
            • Set up
            • Permissions required
            • Mapping options
              • Mapping fix versions
            • Epics ~ our thoughts
            • Additional data syncing
              • Mapping custom fields
                • Company-managed projects
                • Team-managed projects
            • Migrating to epic hierarchies
            • Import using JQL
            • FAQs and troubleshooting
              • Required fields
              • Verify webhooks
              • JQL import issues
              • Workflow issues
              • Ghost cards (cards with a dashed border)
              • Limitations
              • Jira Cloud or Jira Server
          • Jira Data Center (Server)
            • Features
            • Set up
              • Creating an application link
            • Permissions required
            • Mapping options
            • Additional data syncing
              • Mapping custom fields
            • Import using JQL
            • FAQs and troubleshooting
              • Required fields
              • Ghost cards (card with a dashed border)
              • Jira Cloud or Jira Server
              • JQL import issues
          • Azure DevOps
            • Features
            • Set up
            • Permissions required
            • Import using WIQL
            • FAQs and troubleshooting
              • Verify webhooks
              • No Azure DevOps accounts were found for your user
              • Problems communicating with Azure DevOps
              • Work items couldn't be imported
              • Show epics in Azure DevOps backlog
              • Import limits
          • Trello
            • Features
            • Set up
            • FAQs and troubleshooting
          • GitHub
            • Features
            • Set up
            • Permissions required
            • FAQs and troubleshooting
              • What types of GitHub Projects are supported?
          • Linear
            • Features
            • Set up
            • Permissions required
            • FAQs and troubleshooting
      • Notifications
        • Slack
          • Set up
          • Configure notification settings
          • Remove Slack
      • Design tools and media
        • Figma
        • Adobe XD
        • Axure
        • Framer X
        • Invision Web & Studio
        • YouTube & Vimeo
      • Embed Avion
        • Confluence
        • Confluence Server
        • Notion
        • Coda
    • 🔒Security
      • Single Sign-On (SSO)
        • Setup & Configure SSO
        • Azure AD
        • Google Workspace
        • Okta
        • OpenID Connect
      • Two-factor authentication (2FA)
    • ❓FAQs
      • Attachment file types
    • 💳Billing
      • Plans and pricing
      • Legacy plans
      • Free trials
      • Billing and payments
      • Change your plan
      • Cancel your plan
      • Refunds
      • Startup, student and educational discount
  • Story Mapping Guides
    • How To Story Map — A Simple Example
    • Advantages of Story Mapping
    • A Recommended Workflow
Powered by GitBook
On this page
  • What is the projects migration?
  • Why are we making this change?
  • What do I need to do?
  • What happens when story maps are migrated
  • Who can migrate story maps?
  • How long do I have to migrate?
  • What about story maps that aren't used any more?
  • Can I still create story maps outside a project?
  • Can I still manage existing collaborators?
  1. Docs
  2. Core concepts
  3. Projects

Migrating to projects

Last updated 1 year ago

What is the projects migration?

We have added a to Avion that means story maps are no longer rooted to your organization. Instead, they are rooted to a project.

Why are we making this change?

  • You will now be able to give read and write access to a project. Previously, every collaborator had write access to a story map.

  • You can now manage a single project team that has access to multiple story maps. Previously, you had to add everyone as a collaborator to new maps, every single time.

  • Story maps are now more logically grouped — depending on your personal definition of a project.

  • In the future, this will enable us to deliver some awesome features:

    • Share data across story maps (releases, personas, tags, backbones)

    • Enable project-level roadmapping across many story maps

    • Add more modules for better backlog management at the project-level

What do I need to do?

You will need to migrate any existing story maps into a project. We have provided a migration tool that makes this quick and easy. To migrate one or more story maps just do the following.

1) Head to all story maps

Click Migrate story maps

Select one ore more story maps and the desired project

What happens when story maps are migrated

  • The collaborators from each map will be merged down into the project team and given an editor role

  • The story map will be moved into the project

  • The story map will no longer be displayed on the all story maps page

Once a story map is migrated into a project, it can't be moved out or into another project easily. If you make a mistake, please reach out to us at support@avion.io and we can assist.

Who can migrate story maps?

  • The original creator of the story map

  • Organization admins or above

If you need to migrate a story map but don't have the above access, please actively reach out to an organization admin to get this arranged.

How long do I have to migrate?

All story maps will need to be migrated by February 28th, 2023. After this date, any story maps that are not in a project will be automatically moved into a new project named after the creator of the story map.

Example

If a story map exists (that hasn't been migrated) and was originally created by stevejobs, a new project called stevejobs's project will be created, with all story maps from that creator inside. stevejobs will become the lead of this project.

If the creator has since been removed from the Avion organization, we will instead assume that the creator is the Primary Owner.

Lists of collaborators will be lost and you will need to manually add contributors into the project team to gain access again.

We highly recommend you manually move your maps into projects before the deadline, as there will be much less admin for you to do.

What about story maps that aren't used any more?

If you have loose story maps that aren't being used, either create an archive project to store them or delete the story maps. Otherwise, after February 28th, each one will get a new project created for them, as outlined above.

Can I still create story maps outside a project?

No, all new story maps must live inside a project.

Can I still manage existing collaborators?

No, we have removed the management of collaborators. You will need to migrate the story map into a project and then use the project team to allow access.

👏
new projects experience