Print this page

How to Prepare for an Org Migration

Knowledge Article Number 000231870
Description

Last updated on October 19, 2016.

During an org migration, your org moves from one instance to another. If you follow our best practices, this maintenance should be seamless. Below are some frequently asked questions regarding org migrations. Pre & Post org migration checklists attached. 

NOTE: This document is for informational purposes only, and is not part of any legal or otherwise binding agreement. The policies and practices described in this document are subject to change at Salesforce's sole d

Resolution

FAQs
 

1. What action do I need to take to prepare for an org migration?
a. Follow our best practices, outlined on the Salesforce Infrastructure Overview & Best Practices site, to ensure that you are prepared for the maintenance. If you are not following our best practices, your end users may not be able to access Salesforce after the maintenance is complete. Best practices include:
i. Enabling My Domain
ii. Removing Hard-Coded References
iii. Allowing access to all Salesforce IP Addresses


2. What if I don’t follow Salesforce Infrastructure Best Practices?
a. If you are not following our best practices your end users may not be able to access Salesforce after the maintenance is complete. In order to avoid any unintended service disruptions, you may need to take the following actions:
i. If you have any hard-coded references (for example, na1.salesforce.com), make sure that you update them to relative URLs (for example, login.salesforce.com) or implement My Domain prior to the maintenance window. For more information, see the Updating Hard-Coded References article.
1. Hard-coded references will need to be updated with the new instance name within Live Agent following the maintenance.
ii. If you or your team have set up your corporate network settings or email security filters to restrict access to only certain IP ranges or data centers, please ensure that you include our newest ranges. More information on which IP ranges to include can be found in the What are the Salesforce IP Addresses to whitelist? article.
iii. Prepare to refresh integrations if you are experiencing integration issues following the maintenance.
iv. 
Prepare to refresh your DNS cache if you continue to see a “Maintenance in Progress” alert on your login page following the maintenance window.
v. If you locally cache certificates, join the Certificate Changes group in the Success Community to get the latest certificates.

 
3. Will read-only mode be available during the org migration?
a. You will be informed prior to the maintenance regarding your org’s availability during the maintenance window.
b. Read-only mode may be available for a portion or the entirety of the maintenance window.
c. For more information on what read-only mode allows, please see the Read-Only Mode Overview article.


4. Will Salesforce for Outlook (SFO) OAuth tokens be impacted by an org migration?
a. Following the org migration, users should be automatically logged out of SFO and will be prompted to log back in via the Setup Wizard.
b. 
If there are any issues logging back into SFO after the maintenance, follow the steps in the Salesforce for Outlook OAuth reauthentication article.
c. For further questions regarding SFO, post in the Salesforce for Outlook & Email Connect Success Community group.


5. If I plan to view my Email Logs after the org migration, do I need to request my Email Logs before the maintenance window?
a. If you will need to view your Email Logs after the org migration and are moving to a new data center during the org migration, then you need to request your Email Logs prior to the maintenance window. You can request your Email Logs by following the steps in the What are Email Logs? article.
b. 
Once the Email Logs are requested, they will be stored in the database and migrated along with your other data during the org migration maintenance.
c. Email Logs from your former data center cannot be extracted after the org migration.


6. Will the org migration maintenance impact sandbox refreshes?
a. The sandbox refresh queue will be suspended 4 hours before the org migration maintenance begins.
b. If your org was in the midst of a sandbox refresh when the queue is suspended, the sandbox refresh will be stopped. Your sandbox refresh will be restarted (not resumed) 24 hours after the org migration maintenance has completed.


7. Should I refresh my sandbox once the org migration is complete?
a. If the org migration maintenance includes moving to a new data center, we recommend that you refresh your sandbox after the maintenance is complete to ensure your sandbox resides within the same data center as your production instance.
b. 
If you are moving to an instance that is located within the same data center, then a sandbox refresh is not necessary.
c. Customers will be notified via Product and Service Notification emails whether they will remain in the same data center or will be moving to a new data center.


8. Do I need to restart integrations after the maintenance?
a. Restarting your integrations is not required, but if you experience any issues with your integrations following the maintenance, we recommend that you restart them as your first step in troubleshooting the resolution.
i. By restarting your integrations following the maintenance window, you will be clearing the DNS lookup cache which allows your integrations to detect the IP address of the new data center.


9. I use Event Monitoring. Will all event log data be migrated?
a: No, but most will. When the migration starts, data from that day until the day the migration completes (and the org's on the new instance) won't be added to the org in its new location. This is because Event Monitoring relies on log data and a nightly batch process to populate monitoring events.
Example: Migration starts on Friday, Oct 2 at 8:00am. It's scheduled to end on Saturday, Oct 3 at 2:00pm. After the migration completes, data up to and including Thursday, Oct. 1 is moved to the new instance. Also, data is captured from the new instance beginning October 3rd at 2:00pm after the org is activated. Event log data occurring during migration days is unavailable.

 
10. Will the certificates used with my current instance at [INSTANCE].salesforce.com and [INSTANCE]-api.salesforce.com be used with the new instance I am being moved to?
a. Yes, the certificates used for your current instance at [INSTANCE].salesforce.com and [INSTANCE]-api.salesforce.com will remain the same for the new instance.


11. Will the same intermediate, root, and outbound customer-to-Salesforce certificates be used with the new instance?

a. Yes, the intermediate and root certificates will remain the same. Additionally, outbound certificates that are used for SAML, SSO, and APEX will not change.


12. Will routing addresses for Email-to-Case be impacted by the org migration?

a. No, routing addresses for Email-to-Case will not be impacted by the org migration.


13. Will the Salesforce IDs and root-relative URLs of records be preserved?

a. Yes, Salesforce IDs and root-relative URLs for records will remain the same.


14. Do record IDs change at all as a result of an org migration?

 a. No. Existing record IDs will not change after an org migration.


15. How will I know the maintenance windows for the new instance?

a. Review the Preferred Salesforce Maintenance Schedule article to determine the maintenance windows for your new instance.


16. Where can I go for more information on the following topics related to Salesforce maintenance:
i. Email Settings
ii. 
Salesforce IP ranges
i. Hard-coded References
ii. 
Email Thread IDs
iii. WSDLs
iv. 
Certificates
v. Live Agent
i. Weekly Exports
ii. Physical Delete
iii. 
Partner Portals


17. I'd like to learn more about our multitenant architecture. Where can I go?
a. Complete our Understanding the Salesforce Architecture trail.
b. For additional information, read the Multitenant Architecture blog post written by Salesforce developers.


18. Where can I go if I have further questions?
a. For additional questions, you can open a case with Customer Support via the Help & Training portal.
 





promote demote