Skip to main content

Server Migration Checklist: What You Need to Know

Tom S
Updated

Server changes, upgrades, or migrations are common occurrences in today's dynamic business environment. However, these transitions can significantly impact the daily flow of data that EBM ingests from your source systems and ERPs. As your trusted partner in ensuring seamless data integration and integrity, it's imperative that we stay informed of any changes to your server infrastructure. By keeping us in the loop, you enable us to proactively support you through these transitions and minimize any disruptions to your operations. Let's work together to maintain a smooth and uninterrupted data flow.

This article contains the following topics:

Introduction

EBM understands that server migrations or changes can be complex processes, and we're here to support you every step of the way. To ensure a smooth transition and maintain data integrity and integration success, it's crucial to keep us informed. Below, we've outlined the essential information we need from you and how to engage EBM during the migration process.

Notification and Preparation

  • Engage EBM at Least 3 Weeks Prior to the Change:

    If any changes are anticipated, it's crucial to engage EBM at least three weeks before the migration. This lead time allows us to prepare for any necessary development changes and ensure a seamless transition.

Key Questions

  1. Is the Server IP Changing?

    • If yes, please notify EBM in advance.

  2. Is the Server Name Changing?

    • If yes, inform EBM ahead of time.

  3. Is the Name of the Database Changing?

    • If yes, ensure EBM is aware of the change.

  4. Is the Location of the Integration Runtime Agent Going to Need to Change?

    • If yes, please notify EBM promptly.

  5. When is the Migration Scheduled to Take Place?

    • Must inform EBM at least 3 weeks in advance.

How to Notify EBM

  • Contact Information:

    Please reach out to your designated EBM representative or contact our support team directly via support@ebmsoftware.com.

Additional Considerations

  • Testing and Validation:

    We recommend conducting thorough testing and validation of the migration process before the actual switch to minimize any unforeseen issues.

  • Documentation:

    Keep comprehensive documentation of the migration process, including any configuration changes made to facilitate post-migration support and troubleshooting.

  • Post-Migration Support:

    After the migration, don't hesitate to reach out to EBM for any post-migration support or assistance. Our team is here to ensure a smooth transition and address any issues that may arise.

 

By following these guidelines and keeping EBM informed throughout the migration process, you can help us provide the necessary support to maintain data integrity and integration success.

Related to

Related articles

Comments

0 comments

Article is closed for comments.