# Can I add an old Droplet to a VPC without changing its IP address?

Droplets created prior to October 2020 cannot be added to a VPC network without changing its IP address. Any Droplets created since then have VPC functionality enabled by default and are added to the region’s default VPC network unless you specified otherwise during the creation process. You can still add Droplets created prior to October 2020 to a VPC network by [migrating them using snapshots](https://docs.digitalocean.com/products/networking/vpc/how-to/migrate-resources/index.html.md#migrate-droplets-into-a-vpc-network), but they will not retain the same IP information. If you have a domain name directed to the original Droplet, you’ll need to update its DNS records to point to the new IP address.

## Related Topics

[How do I fix a "system not initialized" error on multi-GPU Droplets?](https://docs.digitalocean.com/support/how-do-i-fix-a-system-not-initialized-error-on-multi-gpu-droplets/index.html.md): Make sure NVIDIA Fabric Manager is running and has the same version number as the GPU drivers.

[Why am I getting a Droplet autoscale pool error?](https://docs.digitalocean.com/support/why-am-i-getting-a-droplet-autoscale-pool-error/index.html.md): There may be an issue with the autoscale pool or Droplet configuration, the VPC network’s size, or resource limits on the team or datacenter.

[How to Troubleshoot Load Balancer Health Check Issues](https://docs.digitalocean.com/support/how-to-troubleshoot-load-balancer-health-check-issues/index.html.md): Health checks often fail due to firewalls or misconfigured backend server software.