Unless you are very sure you will continue to have an amicable relationship, I would suggest some kind of internal code audit in addition to having all passwords changed. My little personal hell went something like this in a small business situation (many years ago) ... I am abruptly terminated due to change in ownership and a brief transition period. 10 days later the main server crashed, and all the kings men could not put it back together again (due to really, really poor choices of who was hired). The company went several months without any of the company data (sales, etc). An insurance claim was filed that claimed I left behind a "bomb" that was mysteriously remotely triggered and physically destroyed hardware on one system, deleting all data irrecoverably, and destroyed all the backups (even though externally stored on removable media). In essence the entire system was inoperable and because it contained custom, in house code, could not be rebuilt. The insurance company took this hooey, paid the claim. Then sued me. Some time shortly after this, they replaced all the systems in the business (this was part of the claim I was sued for), and destroyed the original systems thus removing any evidence that might exonerate me. Clever stuff. It was not difficult to prove my innocence to all this utter nonsense, but it took several years and > $10K to get out from under it. Fun stuff.
