diff --git a/journals/2026-06-16.md b/journals/2026-06-16.md
index ebda080..028b00b 100644
--- a/journals/2026-06-16.md
+++ b/journals/2026-06-16.md
@@ -6,4 +6,50 @@ Status: Active
 type: DailyNote
 ---
 
-👍 dzisiaj nie specjalnie robie to co powinienem ale no cóż nie mam serca do tego 
\ No newline at end of file
+👍 dzisiaj nie specjalnie robie to co powinienem ale no cóż nie mam serca do tego 
+
+
+Project migration 
+
+Naser confirmed they have the Excel document needed for the migration steps.
+Paweł mentioned the body will make the decision regarding the migration.
+Project leadership 
+
+Naser confirmed they will lead the project and had a handover meeting with Kamil two weeks ago.
+Migration decisions 
+
+The team decided that the three database clusters will remain in CGI due to potential latency concerns with OVH.
+The team agreed to keep the database clusters in CGI due to latency concerns with OVH
+Project tracking 
+
+Naser emphasized the importance of creating and updating individual tickets for each migration task to demonstrate ongoing work.
+Migration planning 
+
+Participants discussed the SQL Server version requirements for migration, confirming the need for a one-step upgrade path from version 8 to 14 and then to 22.
+Jimmy suggested mounting a new backup drive in VMware and having CGI flip it over to the second server as a standard local drive to speed up the migration process.
+Participants discussed the pros and cons of using a shared backup drive between old and new servers, ultimately deciding that it may not make sense due to cluster differences.
+Paweł confirmed the need for a one-step upgrade path from SQL version 8 to 14 and then to 22 for the migration.
+Participants discussed the specifications for the new server, including CPU, RAM, swap, and backup drive requirements.
+Migration progress 
+
+Paweł confirmed that the databases within the box loop have been migrated to the new server and are disabled in the cluster.
+Jimmy confirmed that Frederick Rodin has already requested new servers and moved the Bart databases.
+Participants agreed to wait until the blue cluster migration is complete before proceeding with additional server orders to avoid unnecessary costs.
+Uppföljningsuppgifter
+
+Uppgift	Tilldelats till	Förfallodatum	Hink
+Restart migration process for the three database clusters in SE (Naser, Paweł)			
+Confirm when the Windows team will prepare the systems for migration (Naser)			
+Set the project due date to October 30th for the migration of the database clusters (Naser, Paweł)			
+Request new servers for the database clusters with specifications copied one-to-one from the old servers (Windows team)			
+Create individual tickets for each migration task and update them as progress is made (Naser)			
+Prepare the list of required database backup disks for migration and send to Naser after the meeting (Paweł)			
+Send the SQL disk configuration details, including number and usage of disks, to Jimmy (Paweł)			
+Prepare the list of required database backup disks for migration and send to Naser after the meeting (Paweł)			
+Send the SQL disk configuration details, including number and usage of disks, to Jimmy (Paweł)			
+Provide the list of required disks for migration to Naser (Paweł)			
+Order new servers for the migration with the listed disks (Naser)			
+Decide backup drive size for the new server, opting for 500 gigabytes for temporary backups (Jimmy, Grzegorz, Paweł, Naser)			
+Submit the server request and push it to Leszek to expedite the CGI process (Naser)			
+
+