# Upgrading older letsencrypt to certbot **URL:** \ **Category:** Server\ **Created:** [December 6, 2017, 1:47am UTC](https://community.letsencrypt.org/t/upgrading-older-letsencrypt-to-certbot/47757 "2017-12-06T01:47:17Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![mnordhoff](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mnordhoff/32/22583_2.png) [@mnordhoff](https://community.letsencrypt.org/u/mnordhoff)\ **Post date:** [December 6, 2017, 2:19am UTC](https://community.letsencrypt.org/t/upgrading-older-letsencrypt-to-certbot/47757/2 "2017-12-06T02:19:22Z")
> [@cooper-rrm](#): > > Can I simply follow these instructions to make the switch? Yeah. > [@cooper-rrm](#): > > I’m assuming that, since I already have the certificates created for my domain and apache is already configured that I shouldn’t run the sudo certbot --apache or sudo certbot --apache certonly commands in those instructions. Is that correct? That's right. Upgrading won't erase your certificates or configuration, and everything should keep working as before. > [@cooper-rrm](#): > > Also, I currently have a cron job (/usr/bin/letsencrypt renew) for auto-renewing my certs with letsencrypt. Once I install certbot, I can remove that job since certbot runs its own renew check, correct? Yes. The Certbot package includes a systemd timer and cron job. (The latter will disable itself since you're using systemd.) If your current cron job includes other options (like a hook to reload a mail server) you'll have to do something about configuring that, though. * * * For what it's worth, the Certbot package keeps `/usr/bin/letsencrypt`. (Replacing it with a symlink to `/usr/bin/certbot`.) So you can start running "`certbot`", but your old "`letsencrypt`" workflow won't stop working. You can run "`certbot renew --dry-run`" to test renewing still works. --- _[View the full topic](https://community.letsencrypt.org/t/upgrading-older-letsencrypt-to-certbot/47757)._