We have an old system, which is a course platform, and we are developing a new version of it, with other technology and some new features.
I am designing the feature that will allow users to migrate content from the old to the new version of the system.
We have already defined that this import can be optional, that is, if he wants to continue using the old platform yet, he can. But I'm in doubt about the friendliest way to offer this to users.
I imagine that working on a concept and wizards is interesting, where each step corresponds to a block of information to be imported, for example:
- Import the courses
- Import modules and classes
- Import students
- Notices and conclusion
At each step, he could select what he wants to import and what he wants to delete, and thus perform the task.
The question is: is this a friendly way of working? is there a model that can be more efficient to reduce friction in this task?