If possible post the video of the up-gradation process
You're not going to lose your policy when you upgrade from upgrade from R77.30 to R80.10.
That said, the policy constructs in R77.30 and R80.10 are different and you'll need to adjust the policy after ugprading to fully leverage all the features in R80.10.
Below is a video that demonstrates best practices when migrating from R77.30 to R80.10 using a real configuration as an example.
If at all possible, I ALWAYS recommend taking a migrate export and import it into a lab environment(VM, test server, etc) and complete the upgrade there first, that way you can go through the entire process and get an idea of what types of issues(if any) you'll more than likely face during the actual upgrade process! One last thing, remember to always take snapshots/backups/migrate exports on a regular basis as best practice recommends!
One of our guidelines at Check Point is to never touch a user's policy structure during upgrades, even if we think it could be optimized. This is because our customers' trust on upgrades and on our management servers is important. So after upgrading to R80.10, all your rules, objects and their enforcement will remain the same, only with nicer colors and better performance.
That being said, things that could change are:
1. Deprecated applications - will remain in the policy but introduce install policy warnings (in R7x these applications were also deprecated)
2. Incorrect database values, such as letters inside a service port number, will fail the pre-upgrade verification process and give you a chance to fix it prior to upgrade.
If you would like to have your policy optimized prior to upgrade, you could use SmartOptimize as described in the video above. Without SmartOptimize your policy will remain exactly the same after the upgrade.
Thanks a lot. Completed the migration successfully and is online now.
Retrieving data ...