For space migration purpose, it's useful if we can import our own data format again.
To migrate a space from instance A to instance b, the Confluence admin can use the Confluence Space export feature. This export doesn't export the related plugin data from our Viewtracker table.
This causes, that the views from instance A from the space aren't migrated to instance B.
We have already the Viewtracker space export feature, where we can export the views of a specific space or even global.
If we could implement a "Viewtracker CSV Import" matching our format we can provide a migration path to the Confluence Admin.
Such an import (running in instance B) needs to do the following:
Search for the new Page in instance B by the Content Title, Content-Type and the Space Key
Search for the user by the Username
Create a Visit with all these objects and the given UNIX Date
If in the CSV the column Source is present, respect this too and import it.
This is an admin task, which could be called in the Confluence administration
It's linked in the more dropdown next to export with the name "import"
It should run in a long-running task
we need to write a log if we couldn't find some users/contents mentioned in the CSV.