FAQ

Yes. Dr Migrate is ISO 27001 compliant and fully GDPR-aligned. Review our security features for more information.

No. All collection operations are strictly read-only. DMC uses only read and guest-operations access, and no changes are made to your environment during or after a scan. The Activity Tracker in Dr Migrate provides a full audit trail of all actions taken. See Security for a full overview of platform controls.

Each customer deployed to the SaaS solution has their solution placed in a dedicated resource group that can be tailored to a specific region. The data for any Dr M deployment is held on the storage account and virtual machine disk / database that resides in that particular solution.

For example, an ANZ customer will currently have all their Dr M solution resources placed within the Australia South East region, each customer will have their own dedicated resource group.

Once a license expires the customer receives a final notification asking if they would like a copy of their data or if they would like to extend their license. If they choose to end their use of Dr Migrate, the managed application and resource group are scheduled for deletion typically within 7 days after which point no data remains. See SaaS Cloud Hosted for full architecture and data residency details.

No third parties have access to Dr Migrate APIs. All API calls are made from the Dr Migrate host on the customer's own Azure tenant. Altra may access the host only in break-fix support scenarios, subject to the following controls:

• Azure Bastion ensures all access is logged and auditable via Azure Activity Logging
• Strict Active Directory controls within Altra limit who can access a customer host
• All data is encrypted at rest and in transit
• Altra is ISO 27001 compliant and fully GDPR-aligned
• Dr Migrate is routinely penetration tested

See Security for a full overview of platform security features.

Dr Migrate supports two primary discovery methods: DMC (Dr Migrate Collector), a standalone scanner you run inside your own environment, and Azure Migrate, which connects to an existing Microsoft discovery project. See Data Collection for full documentation on each method.

If a scan fails or looks incomplete, Dr Migrate generates an interactive diagnostic report immediately after the scan that highlights the problem and can be shared with your team. See the DMC troubleshooting report for details.

DMC (Dr Migrate Collector) is a standalone tool you run from inside your own environment. It scans VMware, physical servers, Hyper-V, Nutanix, AWS, and Azure directly and produces an encrypted output file you upload to Dr Migrate. No Azure subscription is required.

Azure Migrate is Microsoft's discovery appliance. Dr Migrate connects to an existing Azure Migrate project via a Service Principal and reads the data it has already collected. Azure Migrate is best suited for environments already invested in Azure tooling.

The two are mutually exclusive as primary data sources: choose the one that fits your environment.

You can run DMC first and later connect Azure Migrate to enrich the data. Dr Migrate is additive and no existing data is removed. However, this is a one-way move: once Azure Migrate is connected, further DMC uploads may cause duplicate or disconnected records. If you are considering combining both sources, speak to your Dr Migrate contact first. See Data Collection for more on each method.

Yes. Azure Migrate supports discovery of workloads running in AWS and GCP in addition to on-premises environments. Once connected to your Azure Migrate project, Dr Migrate can import and assess those workloads alongside any other discovered assets. See the Azure Migrate guide for setup details.

Only environment-level metadata. No user data, app content, or sensitive info is collected. See Captured Metrics for the full list.

Yes. DMC writes its output to a local encrypted file on the machine where it runs. You can inspect the contents before uploading, and nothing is transmitted until you manually upload via the Dr Migrate portal. See Uploading & Viewing Results for the upload steps.

No. DMC does not transmit data automatically. All uploads to Dr Migrate are initiated manually by the customer admin. See Uploading & Viewing Results for the manual upload process.

A customer admin runs it once using temporary credentials that are discarded post-scan. See Running DMC for step-by-step instructions.

DMC needs read-only vCenter access plus Guest Operations privileges to collect in-guest OS detail. See VMware Requirements for the exact permission list.

Windows requires a Domain or Local Administrator account. Linux requires root or a sudo-enabled user. See System & Access Requirements for the full breakdown by platform.

Yes, but it can be complex to configure correctly and may result in incomplete data if permissions are missing. Admin credentials are recommended for reliability and simplicity. Credentials are never stored and are only used for the duration of the scan. See Security Credential Management for how DMC handles credentials.

Yes. During scan setup you can select specific hosts or import a list to include or exclude particular servers. This is useful for phased assessments or environments where you only need to scope part of the estate. See Running DMC for setup steps.

An interactive diagnostic report is available immediately after the scan. It highlights problems, supports quick troubleshooting, and can be shared with the customer or team.

To avoid data issues from outdated packages. Since DMC runs offline, the expiration ensures users download the latest version. Simply re-download from the portal when needed. See Running DMC for download and setup steps.

Yes. DMC supports multi-vCenter environments. You can add additional vCenter connections during scan setup, allowing you to cover multiple VMware estates in a single scan run. See Scan VMware for setup details.

Yes. See Non-VMware & Physical and Scan AWS for details on each.

Yes. DMC supports Hyper-V and Nutanix in addition to VMware. See Non-VMware & Physical for setup instructions, and check System & Access Requirements for the specific permissions needed for each platform.

Yes. DMC can scan Azure VMs for in-guest OS detail and inventory Azure resources across your subscription. See Scan Azure for the available scan modes and setup steps.

Yes. DMC includes a dedicated SQL scan that collects instance and database metadata to help assess SQL Server workloads for migration. See Scan MS SQL for setup instructions and MS SQL Requirements for the permissions needed.

DMC offers three AWS scan options:

• EC2 Scan: discovers EC2 instances and scans inside the guest OS for installed software, dependencies, and CloudWatch performance metrics.
• AWS Estate Discovery: inventories all AWS services and resources across your account using read-only API access, including cost and usage data. No server credentials required.
• Both: runs EC2 Scan and Estate Discovery together in a single pass. Recommended for most assessments.

See AWS Requirements for the IAM permissions each scan type needs.

Yes, per instance. CloudWatch Agent must be installed and running on each EC2 instance you want memory metrics for. Without it, CPU and disk metrics are still collected but memory is not. See AWS Metrics for the full list of what DMC collects.

Yes. When DMC connects to EC2 instances via SSM, AWS requires an S3 output bucket to store the session output. SSH and WinRM connections do not have this requirement. See AWS Requirements for the full setup details.

Yes. You can run DMC across different data centers or sites at different times and upload each batch separately. Dr Migrate merges the results, so your full estate builds up incrementally without needing a single all-in-one scan. See Running DMC for details.

No. DMC only requires network connectivity to vCenter and ESXi hosts. It does not need access to individual VMs. See System & Access Requirements for the full network requirements.

Possibly. If issues occur, unblock the EXE file after download and consider temporarily exempting it from antivirus like CrowdStrike. Use discretion - these steps are only needed if DMC fails to run. See Running DMC for setup guidance.

DMC does not require any additional network configuration, other than what is outlined in System & Access Requirements.

No. Average CPU usage is less than 2%, scan duration is under 60 seconds, and only read-only commands are used. Pre-checks are performed to avoid scanning during high CPU/memory/disk usage. See DMC for full technical details on how scans work.

No. DMC checks the vCenter logging level beforehand to ensure no adverse impact. All operations are lightweight and non-intrusive. See DMC for full technical details.

You can request a demo or obtain a license through one of our Dr Migrate certified partners. You can also purchase a license by contacting us directly at info@altra.cloud. See Getting Started for an overview of the onboarding process.

Once your license has been provisioned, you have up to 30 days to connect your data. This period is not counted as part of your license term.

Your license term will begin when your data has been successfully connected to Dr Migrate or 30 days after provisioning - whichever date is earlier.

See the Manage SaaS License guide for full instructions.

Open Manage License, select a plan under Renewal License Options, and confirm. Changes apply at your next renewal period. You cannot change your current license term mid-cycle. For SaaS licenses, you also need to complete Azure Marketplace activation before your renewal date. See the Manage SaaS License guide for full instructions.

Your estimated license fees, based on discovered servers, can be viewed under Renewal License Options. Pricing may vary if your server count changes tier.

Note: If you've received special pricing or purchased through a partner, this will not be reflected in the Dr Migrate UI. Contact your partner or Altra contact to confirm pricing.

See the Manage SaaS License guide for how to view and understand your pricing.

You will automatically enter Hibernate mode, a read-only, paid plan that renews monthly at a reduced fee.

Check License Information to confirm if Hibernate Monthly is listed as your Next License.

If you don't want Hibernate, choose a different renewal plan before the trial ends. See the Manage SaaS License guide for how to change your renewal plan.

No. PAYG licenses automatically renew every 30 days and are billed monthly.

Only submit a new request if you're changing plans (e.g. switching to annual). See the Manage SaaS License guide for full details.

Check your renewal details in License Information.

• PAYG plans: auto-renew every 30 days.
• Fixed-term licenses: auto-renew to Monthly PAYG at term end.
• Trial licenses: auto-renew to Hibernate Monthly.

You can change your renewal plan any time before renewal.

To avoid auto-renewal: - Cancel your license (SaaS) - Uninstall Dr Migrate (customer-hosted)

See the Manage SaaS License guide for full renewal instructions.

You'll be notified if your server count exceeds your pricing tier. You'll have 30 days to adjust scope. After that, additional or higher ongoing fees may apply.

You can review server counts and pricing anytime under License Information.

If purchased through a partner: Altra will notify both you and your partner (if contactable) of tier changes. Contact your partner to confirm billing changes.

See the Manage SaaS License guide for how to manage tier changes.

Requests take up to 1 business day to process. You can't change them during that time.

Once processed, you can submit a new request with the correct license plan.

If your request is pending beyond 1 business day, contact admin@altra.cloud with your deployment name and request number.

If purchased through a partner: Contact them immediately and submit a corrected request as needed. See the Manage SaaS License guide for instructions.

SaaS: Go to Manage License and select Cancel your license under Next License. You retain access and are billed until the end of the current period. See the Manage SaaS License guide for details.

Customer-hosted: Follow the Dr Migrate removal guide to uninstall. Billing stops once removed. If purchased through a partner, contact them to confirm billing implications.

Can’t find what you’re looking for? Reach out to us on our Support page. We’re always happy to help!

Yes. Beyond the platform, Altra and our certified partners offer advisory and delivery services throughout your migration, from initial assessment through wave execution. Contact us at info@altra.cloud to discuss your needs.

Our How-to guides library goes beyond the core docs with advanced scenarios: tuning DMC scans, structuring wave plans, configuring TCO benchmarks, and more.

SaaS instances automatically stop after 60 minutes of inactivity to save cost. Signing in restarts the instance and reconnects you automatically - this can take a few minutes. See SaaS Cloud Hosted for more on how SaaS instances work, or contact support if the instance does not restart as expected.

SaaS instances undergo regularly scheduled maintenance on Sundays from 2AM to 10AM in the local time of the servers deployed region. This ensures that the instance stays up to date with regular security updates.

Your instance may not be available during this time window. See SaaS Cloud Hosted for more on how SaaS instances are managed.

When calculating Azure Site Recovery pricing, the cost of the primary region is used. The formula is: ASR flat rate + cost of storage per VM. See TCO Settings to configure your regional pricing assumptions.

The Network Scale tiers include the following line items, priced in the region selected in TCO Settings.

Basic (<1,000 VMs):

Advanced (1,001 - 3,000 VMs):

Enterprise (> 3,000 VMs):

Yes. Backup storage is calculated as a multiple of allocated storage, and this multiplier defaults to 2.5. You can override it in Dr Migrate under Setup → TCO Config → On-Premises Benchmark → Storage Cost (see TCO Settings).

To calculate your own factor:

1. Go to the Azure Pricing Calculator ↗ and load Azure Backup
2. Set storage to 10 GB and configure your backup policy
3. Divide the resulting average monthly backup requirement by 10 (e.g. 17 GB ÷ 10 = 1.7)
4. Enter that value as your backup storage factor and save

A once-yearly backup policy will produce a factor close to 1.0; more frequent policies produce higher factors.