Differences between inMotion Classic and inMotion ignitemail_outline

There are some key differences between inMotion Classic and inMotion ignite, particularly when it comes to how work is created from requests as well as feature terminology. Use this guide to learn more about those differences as you get ready to migrate!

Work Architecture Differences

With Classic, requests can only be turned into projects, which act as folders for related tasks and proofs. But in ignite, there are two types of requests: requests that can be turned into projects, proofs, or tasks, and requests that can be turned into campaigns. If projects are like folders for related tasks and proofs, think of campaigns as folders for related projects. In addition, tasks can also be converted to proofs in ignite, so there's a lot more flexibility in how you can manage your team's work from requests!

Take a look at how the work architecture differs between systems:

Terminology Differences

While a lot of terminology has carried over from Classic, there are a few changes in terminology to familiarize yourself with ignite!

inMotion ClassicinMotion ignite
ContactStakeholder
UserTeam Member
My TeamMembers
Workflow
Route
Review TeamRoute Group
Retrieve ProofCancel Proof
Sequence IDID


We also use the term "work" to refer to tasks and proofs as a whole, and "work items" to refer to individual tasks and proofs specifically.