Server Migration Timeline

Overview

This article outlines Alliant's standard process and timeline for migrating Alliant to a new on-premises server. It includes the prerequisites, planning questions, installation steps, testing, and migration activities required to complete the transition successfully.

Alliant will assist throughout the migration process. Once the new server is installed and available on the network, we typically request 3–4 weeks of lead time to schedule and prepare for the migration. Actual timing may vary depending on your server readiness and project schedule.

Before You Begin

This guide applies to customers who are migrating to a new on-premises (self-hosted) server.

If you are evaluating hosting options, Alliant Cloud is also available as an alternative to maintaining your own server infrastructure.

Alliant Cloud

• Fully managed hosting maintained by Alliant.
• Dedicated private cloud environment for each customer.
• Secure VPN connectivity between the cloud environment and your facility.
• Alliant optional modules are preconfigured and ready to be enabled as needed, such as Alliant Online, Service Web App, and Alliant API.
• Supports standard peripherals and third-party integrations.
• Easily scalable as storage and performance requirements grow.

Self-Hosted (On-Premises)

• Servers and data remain within your organization's network.
• Separate application and web server architecture for secure external access.
• Requires enterprise-grade hardware and ongoing server maintenance.
• SQL Server licensing is managed by the customer.

For additional information, review:

• Alliant Cloud Hosting vs. Self-Hosting
• IT Infrastructure Requirements

Planning and Scheduling

Server migrations are typically scheduled after business hours or on weekends to minimize disruption while all users are out of the system.

Server migration services are considered billable support operations at $175 per hour, with a four-hour minimum. Before the migration begins, Alliant will provide an estimate based on the expected duration and obtain customer approval.

Please keep the Project team informed of your server purchase status and whether the new server has been installed and is available for configuration.

Prerequisite Stage

• Alliant will assign a Project Manager to oversee the migration.
• Install a ScreenConnect session on the new server (Alliant can provide this at no charge).
• Install Internet Information Services (IIS).
• Install Microsoft SQL Server and SQL Server Management Studio.
  • The customer must provide the SQL installation media and license key.
  • Alternatively, the customer may complete the SQL installation and contact Alliant for configuration.
• Create the Alliant folders and network shares on the new server.

Planning Questions

Before the migration begins, be prepared to answer the following:

1. Which server is being replaced (SQL/App/IIS or AII)?
2. Will the server name remain the same?
3. Will the IP address remain the same after installation?
4. Which operating system will be installed?
5. Which version of SQL Server will be installed?
6. Who is responsible for the current server's off-site or cloud backups?
7. Can ScreenConnect be installed for remote access?
8. Will local administrator credentials be provided for the new server?

Installation and Testing

• Install the Alliant application.
• Update Alliant to match the current production release.
• Install the IIS virtual application used by Alliant Mobile for Android.
• Coordinate with third-party vendors regarding any integrations, such as soil counting or garment automation systems.
• Move the server on-site for testing, if applicable.
• Test the desktop application from at least one workstation.
• Test the Android application using the new server.
• Verify network shares used by third-party vendors (for example, Automation Dynamics or Positek).
• Determine whether server names or file paths have changed, which may require workstation updates.
• Schedule the migration with the customer and any third-party vendors (typically about two weeks in advance).
• As a courtesy, Alliant will configure a basic nightly SQL database backup and transaction log shrink.
  • Customers remain responsible for their own backup strategy.
  • Alliant recommends maintaining regularly tested off-site or cloud backups of the Alliant database, application files, or the entire server.

Server Migration

• Schedule a maintenance window during which all users are logged out of the system.
• Handheld devices must complete the day's work and must not retrieve new data until the migration is complete.
• Back up the existing database.
• Restore the database to the new server.
• Test the Alliant application using the new server.
• Set the old database to Offline mode.
• Verify the migration from one or more workstations.
• Update all handheld devices to connect to the new server.
• Perform test retrievals of the next day's invoices to verify connectivity.
• Test any available third-party interfaces, if possible.