Rename a customer, a product or a project in the system, and it stays the same record with its whole history. No second, empty entry appears under the new name, a problem that happens in many other systems whenever a name changes.
The customer, product or project keeps its whole history and still appears only once in every list and report, never twice under the old and new name. A rename always updates the existing entry, never a new one.
If the new name you want is already taken, the system reports that immediately as a conflict, instead of quietly creating a duplicate.
What ports as-is
- Every place a name can change reliably tells apart a new entry from a rename
- A rename needs no separate step of its own: it simply rides along when you edit and save the record as usual
- A name already in use is caught and reported as a conflict immediately
What we build for you
- Which records are renameable in your case
