This comprehensive guide is designed to help customers during server migrations. If you need additional server migration assistance beyond what is outlined in this guide, please contact xchange_support@trimble.com for assistance.
In case you were wondering how much it costs for help with server migrations...
There is no cost to complete a self-service server migration (meaning, if you follow the steps outlined in this guide during normal business hours, Trimble Integrations is happy to help at no additional cost).
All of the information you need for a successful migration is documented below.
Should you require additional support (beyond what is documented below or help with standard procedures outside of normal business hours), Trimble Integrations will assign a resource to assist during the migration for a one-time fee of $1,000.
This fee includes:
- 4 hours of support from a senior technical resource
- Support via phone, email, and live support during evenings/weekends (as needed)
Trimble Integrations standard business hours are 8:00 am - 5:00 pm CST. If after-hours / weekend support is required for this migration, a one-time fee of $1,000 will be required.
To request escalated support, please contact us.
Types of Server Migrations
The term "server migration" can apply to a wide array of infrastructure changes. Select the section below that best describes the type of migration you are performing. If none of these options are suitable, please contact us for assistance.
- Moving only the XChangeAgent to a different server
The database and ERP application are not changing. You are simply changing the server where the XChangeAgent is installed.
- Performing an application upgrade or update; no server name changes
You are upgrading something, but it will not affect the server names, users, passwords, or anything else related to the connection configuration. - Performing a migration that results in a server name change
Moving from on-prem to cloud or data center, moving from old on-prem machine to a newer on-prem machine - Migrating Vista from on-prem to Viewpoint Cloud
You are currently hosting Viewpoint Vista, and are migrating to Viewpoint Cloud - Moving Spectrum from on-prem to Viewpoint Cloud
You are currently hosting Spectrum, and are migrating to Viewpoint Cloud - Upgrading your existing Sage 300 application server
You are migrating or updating your Sage 300 server and installing the latest Sage updates.
- Upgrading your existing Sage 100 application server
You are migrating or updating your Sage 100 server and installing the latest Sage updates.
Moving the XChangeAgent to a different server
Before proceeding, please make sure that:
- You are only moving the XChangeAgent to a different server.
- The server where you have installed the database and ERP application is not changing.
- You are simply changing the server where the XChangeAgent is installed.
Recommended steps for migrating the XChangeAgent:
- First, uninstall the XChangeAgent from the old server. The XChangeAgent can only be installed in one location.
- Contact us and ask us to provide your XChangeAgent Activation Code.
- Once you have the activation code, click here to download the XChangeAgent and install it on the new server. The wizard will walk you through the installation steps, but if you have any questions about the XChangeAgent (installation help, security features, etc.) please refer to our Knowledge Base. Use the Activation Code during installation.
No additional steps are required.
Performing an application upgrade or update; no server name changes
Before proceeding, please make sure that:
- You are doing an in-place upgrade.
- The server name will NOT change.
- Only the software version will be updated. An example is upgrading from Vista 2020 R1.13 to Vista 2021 R2.
Recommended steps for in-place updates:
- Please contact us before you begin so that we can properly turn off your syncs.
- Perform your in-place upgrade.
- Reach back out to let us know you are done. We will test connectivity and reactivate your syncs.
Performing a migration that results in a server name change
Before proceeding, please make sure that:
- You are moving from on-prem to cloud or data center; or
- You are moving from old on-prem machine to a newer on-prem machine; or
- You are changing data centers.
- The server name WILL change.
Recommended migration plan:
- Please contact us before you begin so that we can properly turn off your syncs.
- Perform your migration.
- Reach back out Trimble Integrations to provide the new server name and confirm that the server migration is complete. We will update the connection configuration, test connectivity, and reactivate the syncs.
It is very important that you provide us with the new server name and let us know if any passwords have changed.
Moving Vista from on-prem to Viewpoint Cloud
Before proceeding, please make sure that you are currently hosting Viewpoint Vista, and are migrating to Viewpoint Cloud.
Viewpoint Cloud Migration Plan
Recommended migration plan:
- Contact us before you begin and request the following:
- Turn off all syncs. (This is critical, as we don’t want to export any data to the old location)
- The XChangeAgent Activation Code
- Once the old syncs are turned off, and you have a new activation code, you can uninstall the XChangeAgent from your current on-prem server. You must do this before installing it on the new application server. It cannot be installed in more than one place.
- Viewpoint Support will do all the work to transfer your data and get your new Viewpoint Cloud systems up and running.
- Once the new servers are available in the Viewpoint Cloud, follow these steps and use the Activation Code provided in Step 1 to install the XChangeAgent on the Viewpoint application server:
- After the XChangeAgent has been installed you need to set up SQL user.
If you currently save attachments to Vista, especially if you have a separate database for attachments like VPAttachments, this guide will help.
When steps 1-5 are complete, reach out to XChange so we can test connectivity, update the configuration, and activate the syncs. We will need to know the following:
- Name of SQL user Viewpoint Support created in step 5.
- Example: XChangeServiceUser
- Password for the SQL user they created in step 5.
- Server name where the Viewpoint database is located.
Moving Spectrum from on-prem to Viewpoint Cloud
Before proceeding, please make sure that you are currently hosting Spectrum, and are migrating to Viewpoint Cloud.
Recommended migration plan:
- Please contact us before you begin and ask us to turn off your syncs. This is critical, as we don’t want to export any data to the old location.
- Uninstall the XChangeAgent from your current on-prem server.
- Submit a request to Spectrum to whitelist our IP address. The instructions for this can be found here:
- Once Spectrum has confirmed that your Cloud environment is up and running AND Trimble's IP addresses have been whitelisted, reach back out to us to inform us that your migration is complete. We will also need the following information:
- Server URL: <<companyname-data>>.dexterchaney.com
- Database: Forefront or Spectrum
- Name of Infolink User
- Password for the Infolink. Let us know if the password is changing. “Enforce password policy” MUST be disabled on the user’s profile.
Please continue reading below if:
- You intend to leverage an FTP site hosted by Spectrum (required for Concur receipt images)
- Subscribe to an integration that will require the Data Exchange module (This is required when Trimble Integrations is automatically inserting data INTO Spectrum on your behalf. This is not required if we are only providing you import files.)
Spectrum FTP
If the integration that you subscribe to (example: Concur) requires us to send files to an FTP site, moving to the Viewpoint Cloud environment will require Viewpoint to host this FTP site on your behalf going forward.
Steps that need to be taken:
- Reach out to Viewpoint support and request that they set up a temporary directory on the Spectrum server for purposes of storing images prior to importing them into Spectrum
- Once Viewpoint has set up the FTP site, we will need the following information:
- FTP Server URL: clientftp.dexterchaney.com
- Login ID
- Password
- Port number (usually 21)
Data Exchange Module
If Trimble Integrations is automatically inserting data into your Spectrum database, the Data Exchange Module will be required if it is not already set up.
- This does not apply to: Concur
- This does apply to: BambooHR, Agora, ServiceTrade
Steps that need to be taken:
- Complete the Data Exchange URL and ID setup by following the instructions here.
- Once complete, reach out to Trimble Integrations and provide the following information:
- Authorization ID created in Part 2.
- Example: RYV1234
- The URL and Port Number from Part 3.
- Authorization ID created in Part 2.
We will test connectivity, update the configuration, and activate the syncs.
Upgrading your existing Sage 300 application server
Before proceeding, please make sure that you are migrating or updating your Sage 300 server and installing the latest Sage updates.
Recommended migration plan:
- Uninstall the XChangeAgent from your current server. The XChangeAgent can only be installed in one location.
- Contact us and ask us to provide your XChangeAgent Activation Code.
- Install the XChangeAgent on your new server. To do so, just click here to download the XChangeAgent. The wizard will walk you through the installation steps, but if you have any questions about the XChangeAgent (installation help, security features, etc.) please refer to our Knowledge Base. Use the Activation Code during installation.
- After the XChangeAgent has been installed, set up a User for the XChangeAgent in your Sage 300 CRE production application (instructions here). You may be able to skip this step if the Sage users are migrated already.
- When all of these steps are complete, reach out to us so we can test connectivity and update the configuration. We will need to know the following:
- Name of user you created in step 4. Example: XChangeServiceUser
- Password for the user you created in step 4, if it has changed
- Path to the Sage 300 data folder.
- Example: \\SERVER2\Timberline Office\Data\COMPANYNAME\
Upgrading your existing Sage 100 application server
Before proceeding, please make sure that you are migrating or updating your Sage 100 Contractor server and installing the latest Sage updates.
Recommended migration plan:
- Uninstall the XChangeAgent from your current server. The XChangeAgent can only be installed in one location.
- Contact us and ask us to provide your XChangeAgent Activation Code.
- Install the XChangeAgent on your new server. To do so, just click here to download the XChangeAgent. The wizard will walk you through the installation steps, but if you have any questions about the XChangeAgent (installation help, security features, etc.) please refer to our Knowledge Base. Use the Activation Code during installation.
- After the XChangeAgent has been installed, set up a User for the XChangeAgent in Sage 100 Contractor. You may be able to skip this step if the Sage users are migrated already. (Instructions here)
- When all of these steps are complete, reach out to us so we can test connectivity and update the configuration. We will need to know the following:
- Sage 100 Database Path
- Example: SERVER1\SAGE100CON
- Sage 100 Database Name (often your company name)
- SQL Username
- Example: API - User
- SQL User password
- Sage 100 Database Path