In case you are transferring your domain, the system considers this email address to be a new user who is not a part of your workspace yet.
So the logic here is the following: you would need to invite this new user into the system, and reassign everything that should belong to them: records, tasks, workflows, etc.
Here is a step-by-step instruction of what has to be done:
Add a neutral Gmail account before you change the domains (if you don't already have it in your workspace) - make it an admin and then you will be able to invite the rest (in order not to lose access). This will be the user who can invite/remove everyone later on and reassign everything.
Add the new user to the workspace (the new email address you are changing to) to the Admin role.
Please note: when adding a new user the system will warn you about the charge for an extra user, but if you remove an old user the same day (Step 5) you will NOT get charged.
Log into NetHunt under the new account and accept the invitation.
Once the new user (new email account) is in the workspace, you will need to reassign all the modules that were assigned to the old account to the new one that you are adding. You can start with records reassigning: here is the guide on the mass update of the records.
Tasks: except for reassigning the records, you should also reassign all the tasks that belonged to your old user:
6. Workflows: please note that if you had workflows created/active under your old user, and you try to delete him/her, here is a notification you will receive from the system:
So, before removing your old Gmail account, please make sure to deactivate and finish up all of the workflows that were created under your old user. In this way, no new records will be triggered in this particular automation, but the active runs will be completed:
If you need the same workflow to keep running under your new user, please change the ownership to the new user:
7. As an additional step, it’s recommended to review which integrations are currently active for the email address being deleted. Make sure to check if this user is listed as the integration owner in tools like Zapier, your VoIP system, Looker Studio, or any other connected services.
8. Once you are done with all of the steps, go to the Users section and remove the one you no longer want to be in the system. Do not forget this step, or you will be charged for the user who is no longer working in the CRM:
Haven’t found the answers you’re looking for? Ask our Users Community.