In many companies the IPv6 migration has already happened. For those that have not started yet it will be more expensive if they wait even longer.
The hardest part seems to be training people. IPv6 is different - it is more than just "longer addresses".
It is a newer protocol that fixes many more problems with IPv4 than just address exhaustion.
So this "ipv6 migration" is actually an opportunity to leverage those new features.
Designing IT infrastructure IPv6 first and IPv4 second allows for so much simpler designs.
You can have your complete network IPv6 only and do IPv4 on the edge for legacy clients. (Maybe doing outgoing NAT for v4 where required)
The results are a much cleaner layout (because of the larger address space), simpler firewall rules, and so on.
It is not complicated or hard to do (in contrary I think that e.g. just setting up SLAAC is much simpler than managing DHCP) but the engineers need to know how it is different.
They need training for that. People are often used to the old ways, once they have seen and worked with IPv6 it is no problem.
I've helped larger and smaller companies since ~2004 with those migrations.
One observation I've made is that here in europe IPv6 is a basic fact of networking where as in the US it appears as if many companies are in denial.
That cloud providers like AWS don't do native v6 is absolutely ridiculous.
When you write code or security rules today that is not designed with IPv6 in mind they are outdated today. Don't do it ;-)
The hardest part seems to be training people. IPv6 is different - it is more than just "longer addresses". It is a newer protocol that fixes many more problems with IPv4 than just address exhaustion. So this "ipv6 migration" is actually an opportunity to leverage those new features.
Designing IT infrastructure IPv6 first and IPv4 second allows for so much simpler designs. You can have your complete network IPv6 only and do IPv4 on the edge for legacy clients. (Maybe doing outgoing NAT for v4 where required) The results are a much cleaner layout (because of the larger address space), simpler firewall rules, and so on.
It is not complicated or hard to do (in contrary I think that e.g. just setting up SLAAC is much simpler than managing DHCP) but the engineers need to know how it is different. They need training for that. People are often used to the old ways, once they have seen and worked with IPv6 it is no problem.
I've helped larger and smaller companies since ~2004 with those migrations. One observation I've made is that here in europe IPv6 is a basic fact of networking where as in the US it appears as if many companies are in denial. That cloud providers like AWS don't do native v6 is absolutely ridiculous.
When you write code or security rules today that is not designed with IPv6 in mind they are outdated today. Don't do it ;-)