Customer migrations: Prioritising service uptime through mini projects
As part of our ongoing investment in the cloud, Aspin recently migrated all of our shared DataBridge customers into our cloud environment; consolidating many separate physical servers into a centrally managed, flexible, resilient cloud infrastructure — powered by Amazon Web Services (AWS).
An infrastructure change such as this, although transparent to customers, carries some risk so rather than rushing it through we treated the migrations as mini projects which were scheduled with our customers and managed through our internal Projects Team. Typically, our process looks like this:
A Project Specialist communicates the customer-specific migration plan to each customer, schedules the migrations around non-critical times, schedules user acceptance testing, has a roll-back plan in place, and staggers the migrations to ensure we have the support capacity to handle any potential migration issues.
Managing the migrations in this way has meant minimal disruption and put the needs of our customers first. The key objectives for any migration are as follows:
- prioritising uptime
- minimising risk
- ensuring a smooth transition to the new environment
A similar approach is now being taken with our migrations to SkooCloud for PixSell and InterSell image distribution. This focus on customer uptime, customer service and clear, transparent communication underscores everything we do and is baked into our roadmap (and into our DNA!).
Over the last 33 years we’ve built a reputation for high-quality applications, continuity, and long-term business relationships which we value immensely. This approach underpins how we undertake customer migrations and how we execute on our our long-term software strategy.