Infrastructure
Environment & Setup
DMM 9 doesn't care where your database lives. It works on-premises, in the cloud, and on OutSystems PaaS, as long as it can connect with the right permissions.
What DMM 9 Needs
DMM 9 needs a way to reach your source and destination data with the right permissions. On-premises or self-managed cloud, that's a connection string for each. On OutSystems Cloud and PaaS, DMM 9 uses the platform's own connection feature, so you don't manage connection strings yourself.
Supported Migration Paths
DMM 9 handles migrations between any combination of on-premises and cloud environments. All paths are bidirectional.
Setup Options
Choose the setup approach that matches your infrastructure.
On-Premises / Self-Managed Cloud
Direct database access with standard connection strings. DMM 9 connects directly to your source and destination databases.
OutSystems PaaS
Uses the OutSystems Runtime Connection Feature to access databases managed by the PaaS platform.
Any Infrastructure
DMM 9 works with any infrastructure as long as it can reach the data with the required permissions, through a connection string or the OutSystems platform.
Getting Started
Three steps to begin migrating data with DMM 9.
Set up access
For on-premises or self-managed databases, that's a connection string for the source and one for the destination. On OutSystems Cloud and PaaS, DMM 9 uses the platform connection feature instead.
Deploy DMM 9
Install DMM 9 in your OutSystems environment via Forge. It deploys within your own infrastructure.
Configure & Validate
Set up your source and destination connections, configure migration mappings, and run the built-in validator.
Need Detailed Instructions?
Check out the official DMM 9 User Manual for step-by-step guidance, or reach out to our team for support.