This page provides an overview of the Lobster Cloud migration process: supported migration scenarios, what Lobster provides, your responsibilities, and the technical prerequisites. For the complete process including on-premise preparation, see Migration process step by step.
Migration Scenarios
Scenario | Description |
|---|---|
On-Premises to Lobster Cloud | Migration from a self-hosted Lobster installation to a fully managed Lobster Cloud environment. |
Lobster Cloud Standard to High Availability | Upgrade from a standard cloud environment to an High Availability architecture. This is a new installation with a clean migration. |
Lobster Cloud to Lobster Cloud | Migration between Lobster Cloud environments (e.g. region change or architecture upgrade to HA). |
What Lobster Provides
Service | Details |
|---|---|
Cloud infrastructure provisioning | A new Lobster Cloud environment is set up with the latest available software version. |
Base configuration of infrastructure and software | Lobster assists with infrastructure configuration and basic software setup, including the configuration of your own email server, SSH and AS2, as well as other settings and services that cannot be configured through the user interface. |
Standard DNS and SSL | DNS names under the |
Documentation and training | Technical documentation for your new environment and training on the migration tools. |
VPN setup (if required) | Site-to-site VPN connection between your on-premise network and the new cloud environment. |
Your Responsibilities
Responsibility | Details |
|---|---|
Perform data migration | You use Transport Manager and Meta Exchange to transfer profiles and configurations from your existing system to the new cloud environment. |
Ensure version compatibility | Your on-premise system must be compatible with the software version of the cloud system. Update your on-premise system before starting the migration if required. See Migration process step by step. |
Adjust network settings | Configure firewall rules and network settings on your side. Full details under Network and connectivity. |
Provide SSL certificates(if applicable) | If you want to use your own DNS names, you must provide your own SSL certificate. |
Technical Prerequisites
Version Compatibility
Your System | Requirement |
|---|---|
Lobster data and/or Lobster pro | Upgrade to the latest Lobster Data Platform (LDP) version required. |
Migration from an older version is technically possible but makes the process unnecessarily complex. The recommendation is therefore to bring your on-premise environment up to the current version before starting the migration. Full details on the upgrade path can be found under One-click migration from older systems.
Supported Migration Methods
Supported | Not Supported |
|---|---|
Profile transfer via Transport Manager | Direct database imports or dumps |
Configuration transfer via Meta Exchange | File system transfers |
Optional Migration Support
If you need assistance with your migration, Lobster offers optional consulting and support services. Please reach out to your Lobster Sales contact, Account Manager, Technical Success Manager (TSM), or Customer Success to discuss available support packages.
Information for Orchestration Customers
If you are migrating from a Lobster _pro (Orchestration) system:
Aspect | Details |
|---|---|
Configuration transfer | Orchestration configurations can be transferred via Meta Exchange. |
Transaction data | Migrating transaction data requires a separate consulting project and is not covered by the standard migration process. |