Skip to main content
Mitratech Success Center

Client Support Center

Need help? Click a product group below to select your application and get access to knowledge articles, webinars, training content, and release notes or to contact our support team.

Authorized users - log in to create a ticket, view tickets status and check your success plan details.


On-Premise TeamConnect Environment Refresh Best Practices and Suggestions

TeamConnect Upgrades Included Environment Refresh Best Practices and Suggestions

1. Note that when you refresh Production data down to a lower environment, the data and configs in the lower environment will be replaced. This means if there is any configuration work you have been doing in this lower environment that you want to save, you will need to copy those configurations down BEFORE the refresh to preserve those items.

2. Integrations – Note that any integrations between TeamConnect and third-party applications might be affected by the refresh of PROD to the lower environment. Any integrations that have PROD “pointers” or references located in the integration settings will mean that those settings will then appear after the refresh of PROD to the lower environment. Remember after the refresh to change those “pointers” or configs that refer to PROD to reflect the lower environment.

3. TC Document considerations – You will need to copy over system documents to the lower environment(s) since these documents are integral to the functionality of customizations in TC. These are documents in the “Top Level / System” folder and subfolders. You do not necessarily have to copy the remainder of the documents from Prod to the lower instance.

4. Do you have SSO and use SAML? A user with access to documents needs to back up the files in these directories. They should also take note of the folder structure, and if needed re-create the paths after the maintenance is complete. SSO will not work in the lower environment until these files are replaced.



5. Outgoing mail server: You will want to disable the outgoing SMTP mail server in the lower environments to prevent emails from being sent.

6. Run script to replace valid email addresses with dummy email addresses (to prevent notifications from accidentally going out from the lower environment.) This is important for when you want to re-enable outgoing emails for testing. You can change the email addresses in contacts for only those items you want to test.

7. Disable all Scheduled Actions in the lower environment after refresh.

8. Remember that the database refresh means all users would need to use their credentials from PROD to log into the lower environment.

Here is an example of the stop notifications script that our hosting team runs. Please use this just as a guide as to how the team accomplishes these stop notifications. Changes may need to be made to your script according to your environmental needs.





  • Was this article helpful?