Skip to main content
Skip table of contents

Salesforce Server Migrations with Nimble AMS

At a particular age, Salesforce will replace their servers and migrate organizations, generally Production instances, to a new server - because of this, they have their own set of generic best practices. With Nimble AMS, there are a few additional best practices to follow that will help provide a smooth transition in the event your Organization is migrated.

Learn more about Salesforce's Instance Migration Best Practices (external)

Nimble AMS Best Practices

Though there is not much by default to check in Nimble AMS, there are still sections of a Production Environment that should be looked into in the event that you are being moved to a different server. Many of these manual checks can be avoided by enabling My Domain; if this is the case, it will be noted; however, if My Domain is newly implemented or you would like to be extra secure, we do recommend reviewing each of these sections.

  1. Custom Links/Buttons

    1. If you do not have ‘My Domain’ enabled and use custom links/buttons in Staff View that redirect to specific pages that note the server within the URL (such as a custom report link, dashboard link, et cetera), you will want to prepare to change these after the server move. As these refreshes/moves tend to happen over the weekend, you may be able to adjust these at the end of the day the Friday before your scheduled transition.

  2. Fields Containing Links
    1. Similar to Custom Links/Buttons, if you use links in fields on records that include the Salesforce Server, you will want to update these to ensure they still work after the Server Migration - not adjusting or accounting for these changes can cause broken links or images to appear in Constituent Facing areas, such as Community Hub. If My Domain is enabled, and the links use the My Domain URL, you will not need to make adjustments.

  3. Email Templates
    1. If you do not have My Domain enabled and use non-merge field links within Email Templates for components such as Community Hub, this will need to be manually updated as well to match the new Salesforce Server Pod. 

  4. Remote Site Setting and Content Security Policy Trusted Sites
    1. RSS like the DocuSignSFDCSoapApi or Trusted Sites as part of Content Security may also include the server within their URLS; if My Domain is enabled and sites use this rather than the Salesforce Server, or outside links such as websites linked via Single Sign-On, you should not need to worry about this.

  5. Server Backup
    1. Though the chances are very, very low that data may be lost during a server migration, it is still a good idea to ensure you complete a Data Export a few days before the Migration is meant to happen. This ensures that, if data is lost, you are only losing a few days worth of data, if anything at all.

Pre-Instance Migration Checklist (external download)

Post-Instance Migration Checklist (external download)

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.