NOTE! If you have been directed here from a banner in your Next, you need to take action. Please read from the heading "Do I have conflicts?" below.
What is happening?
During the fall of 2026, we will complete the transition from the old project journal (Journal) to the newer version Journal 2.0 in Next Project. This process requires us to migrate all data from Journal to Journal 2.0.
The goal is to consolidate all diary functionality into one solution.
Why are we doing this?
Journal 2.0 is the solution we will continue to develop going forward. To offer full functionality, better reports, and a unified view, all historical data needs to be in the same module.
What does this mean for me?
For most customers, the transition will occur without significant impact. Views will be retained but consolidated under the current Journal 2.0 and will be controlled by a new project setting. After the migration, all mobile diary reporting will take place from the new Next Mobile (Next Webapp).
We are currently analyzing existing databases to ensure that all information is migrated correctly. In some cases, we have identified situations where information is registered both in Journal and Journal 2.0. These customers will be contacted separately with more information and any choices or actions that need to be taken before the migration is carried out.
Am I affected?
All customers who have used the old version "Journal" are affected by the migration to Journal 2.0. Which of the scenarios below applies to you determines if you need to take any action.
Which scenario applies to me?
| Scenario | What happens during the migration |
| You have only used Journal 2.0 | You are not affected by the migration itself. You will gain access to new functionality in Journal 2.0. |
| You have used Journal previously and then switched to Journal 2.0 without duplicate entries | We will automatically migrate all data from the old Journal to the new Journal 2.0. No action is required from you. |
| You have used both Journal and Journal 2.0, with entries in both on the same day and project | The same automatic migration as above applies, except for the days where duplicate entries have been identified. For these days, we will contact you separately with information on how the conflicts will be handled. |
Do I have conflicts?
Customers with identified conflicts (scenario 3 above) will be contacted separately via email with an attached list showing which projects and dates are affected. If you have not received such an email, there are no known conflicts in your database.
What do I need to do if I have conflicts?
We recommend that you review the affected projects yourself and remove the data (in Journal or Journal 2.0) that is no longer current:
- Check which of the entries is correct for each day.
- Remove the incorrect or outdated entry.
- When only one entry per day and project remains, the migration will proceed automatically and correctly.
What happens if I do nothing?
If no action is taken before the specified date, we will:
- Migrate data from Journal to Journal 2.0 where there are no conflicts.
- Keep conflict data from Journal 2.0.
- Remove conflict data from the old Journal.
- Provide PDF reports from Journal for archiving.
Days where entries exist only in one module will not be affected and will be retained regardless.
We have a banner in our database prompting us to resolve duplicate data, but I have not received any email
The email has probably been sent to someone else in your company. Contact support and they can assist you further.
What happens with the personnel register?
In connection with the discontinuation of Journal, the personnel register function linked to it will also be discontinued. The function no longer meets current requirements and therefore will not be transferred to Journal 2.0 in its current form. We ask you to ensure that personnel registration at the workplace is done in a way that meets current requirements, for example via Rekyl’s free version: https://personalliggare.rekyl.nu/.
What happens going forward?
In the coming months, we will:
- Inform affected customers that we have identified some entries that need to be reviewed and handled before the migration.
- Carry out the migration of Journal data from Journal to Journal 2.0.
- Continue developing functionality in Journal 2.0 to eventually have a unified view regardless of reporting level in the Journal (project or WO/VO).
Do you have questions?
If you have questions about the transition, you are welcome to contact our support team.