SYNCHRESIS SOLUTIONS
VMWARE MIGRATION AND VIRTUALIZATION EVALUATION WORKSHEET
Revision: 2026-10-19

An ungated planning worksheet for IT decision makers and engineers.
Use one copy per candidate platform. Share a copy with your application owners.
Keep sensitive infrastructure details in your organization's approved systems.

SYNCHRESISVM PRICING AND CLOSED-BETA OFFER
FREE SINGLE-SERVER BETA, INSTALLED FOR YOU.
Single-server software, installation, support and direct developer access cost $0
during closed beta.
We install it for you so you can judge the platform for yourself.

Native desktop apps for Windows, Linux and macOS are free forever. Every VM type
available on SynchresisVM Server is easy to run in the desktop apps. They can also
connect to a remote Server. Available local backends depend on the host OS.

The FreeBSD ISO and packaged install include the full QEMU suite alongside bhyve.
bhyve is the default for hardware-assisted virtualization; QEMU's TCG provides
software emulation. QEMU and 86Box offer options for older guest operating systems
and software that depends on period PC hardware, including legacy CAD workloads.
SynchresisVM does not bundle proprietary firmware. Required proprietary BIOS or
device firmware must be obtained separately.

SynchresisVM Server is free forever for single-server use, including the official
1.0 release. Clustering costs $295 per server per year, including expert support
directly from the developers. A cluster requires at least two licensed servers:
$590/year minimum. Every cluster member is licensed, including the first.
We can demo clustering on the installation call at no charge. Free trials for
small clusters may be agreed individually for the duration of closed beta.
Standard clustering prices apply unless we have agreed a trial with you.

Clustering requires active licences and online licence validation. Air-gapped
arrangements are available only by agreement with us. If cluster licence payments
lapse, servers revert to standalone operation without interrupting running
workloads. Load balancing, migration between hosts and other cluster operations
are unavailable until payment is resolved and the licences are active again.

Two-server clusters are supported, with no rigid-quorum requirement. Every Server
installation is a first-class cluster node regardless of host CPU architecture
or manufacturer. Live migration is available wherever the backend, VM
configuration and participating hosts permit it.

SynchresisVM Server supports shared storage over NFS and NVMe over Fabrics
(NVMe-oF). All core x86 and x86_64 VM types also support shared-nothing live
migration: move a running VM and its disks between SynchresisVM hosts using local storage,
without a shared-storage system.

Single-server support is included free during closed beta, without an SLA by
default. As our thanks for their help, beta participants keep this free support
for 90 days after closed beta ends. After closed beta, all single-server users
can purchase per-incident support billed hourly at a rate lower than our general
expert-support rate. Beta participants retain their 90-day free support period.

Cluster licences include unlimited developer support for the licence term,
without an SLA. Our target is an engineer working on your issue within four hours.
Engineering support is also available for macOS and Windows Server builds,
including builds we do not routinely maintain or test. Single-server use follows
the same beta and post-beta support terms above.
For an annual fee, we can arrange an SLA as short as 15 minutes to an experienced
VM infrastructure engineer working directly on your issue, during Monday-Friday,
8 a.m.-8 p.m. US Eastern. That always means an engineer who regularly solves VM
infrastructure problems and has restored service through serious production
outages. An optional contract can lock in your annual price. Optional SLAs and
separately purchased support are quoted separately.

Installation calls are a separate introductory offer: free throughout closed beta
and for the first few months after 1.0. No purchase required. You work directly
with the developers to get installed and ask questions. White-glove workload
migration is a separate service at $15 per VM, targeting minimal downtime and
including testing after first boot.

SynchresisVM is available now in closed beta. Book your installation call
directly at https://synchresis.net/schedule and put "SynchresisVM installation" in
the agenda, or use the beta request form if you prefer us to get in touch.
Evaluate every candidate against your own requirements and retain the evidence.
This worksheet does not certify compatibility or establish production readiness.

Accompanying guide: https://synchresis.net/vmware-migration-checklist
Product: https://synchresis.net/synchresisvm
Server installation options and support status:
https://synchresis.net/synchresisvm#server-options
Pricing: https://synchresis.net/synchresisvm/pricing
Request access: https://synchresis.net/synchresisvm-beta
Book an installation under the introductory offer: https://synchresis.net/schedule

1. DECISION AND ACCOUNTABILITY

Organization/project:
Candidate platform and exact version/build:
Evaluation date:
Business sponsor:
Technical lead:
Application owners:
Security/recovery reviewer:
Cutover decision owner:
Planning or deployment deadline:
Evaluation window:
Budget and comparison period:
Workloads in scope:
Workloads excluded, with reason:

Business outcome sought:
Mandatory availability requirements:
Maximum tolerable data loss (RPO), per service:
Maximum time to restore service (RTO), per service:
Maximum cutover interruption, per service:
Required support coverage and escalation:
Application-vendor or regulatory requirements:

2. DEPENDENCY INVENTORY

Identify services and their dependencies before selecting migration batches.
Use an internal reference instead of attaching credentials or sensitive data.

For each service, record:
- Service name, business owner, criticality and acceptance tester.
- VM names/counts, guest OS versions, firmware (BIOS/UEFI), guest tools.
- CPU architecture/features, allocated and observed peak CPU/memory.
- Application/database versions and vendor support requirements.
- DNS, identity, databases, queues, certificates and external integrations.
- Datastores, disk sizes/controllers, snapshots, vSAN, SAN/NAS, RDM/shared disks.
- Encryption, key custody, vTPM and any special recovery requirements.
- VLANs, addresses, routes, NSX/firewall rules and load balancers.
- GPU or other device passthrough and hardware dependencies.
- HA/DRS/vMotion requirements and actual maintenance procedures.
- Backup/replication tools, retention, restore procedure and recovery targets.
- Monitoring, identity/RBAC, logging, patching, templates and automation.

Dependency record:
Service | Depends on | Owner | Migration order/constraint | Evidence reference
________|____________|_______|____________________________|___________________

3. REQUIREMENTS AND EVIDENCE REGISTER

Every draft requirement below starts PENDING. Add your exact version, threshold,
owner and evidence. Mark it mandatory or preferred before testing.

Status definitions:
PENDING = evidence is missing, incomplete, or not applicable to our environment.
PASS = agreed requirement is satisfied by reviewed evidence.
FAIL = agreed requirement is not satisfied.
N/A = formally removed from scope, with owner and reason recorded.

ID | Draft requirement | Mandatory/preferred | Evidence to collect | Status
01 | Guest OS/application compatibility | TBD | Version-specific support and application test | PENDING
02 | Firmware, drivers and boot | TBD | Successful boot and guest/device checks | PENDING
03 | Host and special-device compatibility | TBD | Exact hardware validation | PENDING
04 | Disk transfer and data integrity | TBD | Tested procedure and application/data verification | PENDING
05 | Network and security mapping | TBD | Allowed/denied paths and access tests | PENDING
06 | Performance and capacity | TBD | Agreed workload and measured baseline comparison | PENDING
07 | Backup and restore | TBD | Restored application, recovery point and elapsed time | PENDING
08 | Failure and maintenance behavior | TBD | Required lab exercises and recovery results | PENDING
09 | Monitoring, logs and escalation | TBD | Alert delivery and operating runbook | PENDING
10 | Identity and administrator roles | TBD | Access and least-privilege checks | PENDING
11 | Automation and integrations | TBD | Required workflow execution | PENDING
12 | Updates and daily operation | TBD | Maintained/tested procedure and owner | PENDING
13 | Cutover window and rollback | TBD | Timed rehearsal and reconciliation plan | PENDING
14 | Support and vendor requirements | TBD | Written terms and applicable approvals | PENDING
15 | Cost and staffing | TBD | Dated quotations, assumptions and staff estimate | PENDING

Detailed evidence record (repeat for every requirement):
Requirement ID:
Owner/reviewer:
Mandatory or preferred:
Exact acceptance criterion and threshold:
Source/destination versions and configuration:
Test date, procedure and representative workload:
Observed result:
Evidence reference:
Status:
Unresolved issue/action/owner/due date:
Acceptance name/date:

4. REPRESENTATIVE PILOT PLAN

Representative services selected and reason:
Authorized test data and handling requirements:
Network isolation and duplicate-identity protections:
Source versions/configuration:
Destination versions/configuration:
Transfer method and documentation reference:
Storage and network mappings:
Firmware/controller/driver changes:
Prerequisites and capacity checks:
Required application tests and owners:
Performance baseline and workload definition:
Backup/restore test and target RPO/RTO:
Failure/maintenance exercises required:
Runbook reviewer who did not write the procedure:

Record elapsed time for preparation, transfer, first boot, corrections,
application validation, restore and rollback. Keep errors and manual steps.
Do not treat a VM boot, disk conversion, or a vendor feature description as
proof of end-to-end application operation.

5. GO / STOP DECISION

GO requires all of the following:
[ ] Every mandatory requirement has reviewed PASS evidence, or an explicitly
    approved scope change with the accountable owner's name and reason.
[ ] Application owners have accepted real client workflows and data checks.
[ ] Backup restore and required recovery behavior meet the agreed RPO/RTO.
[ ] Cutover and recovery fit the approved window.
[ ] Staff can operate the environment using the recorded runbook.
[ ] Support arrangements, costs, ownership and escalation are understood.
[ ] Rollback has been rehearsed and post-cutover writes are accounted for.

STOP for unresolved data errors, unsupported mandatory dependencies, missed
recovery targets, or unknown rollback behavior. A favorable average cannot
override a failed mandatory requirement.

Overall evaluation status: PENDING
Mandatory passed: ___ of ___
Mandatory pending: ___
Mandatory failed: ___
Preferred requirements assessment, if useful:
Decision: NOT YET MADE
Decision owner/date:
Outstanding actions:

6. CUTOVER AND ROLLBACK RECORD

Service/dependency group:
Approved window and affected users:
Usable backup and verified restore evidence:
Write-quiescence/consistency procedure:
Migration sequence and responsible engineers:
Client-facing acceptance tests and application owners:
Go/no-go deadline (leave enough time to recover):
Objective rollback triggers:
Recovery procedure and measured duration:
Authoritative system at each stage:
How simultaneous writers are prevented:
How post-cutover writes are preserved or reconciled on rollback:
Communications owner and status checkpoints:
Old-environment retention and eventual retirement criteria:
Application-owner acceptance:

Never assume restarting the old VM is sufficient rollback after users have
written data on the new platform. Rehearse the recovery and reconciliation
procedure in isolation before approving the change.

7. WHOLE-COST COMPARISON

Use the same period, workload and service assumptions for every candidate.
Mark each number PRICED, QUOTED, MEASURED or ESTIMATED; include date and source.

SynchresisVM pricing used in this worksheet (2026-10-19):
https://synchresis.net/synchresisvm/pricing

Choose the single-server or clustered configuration that applies. The rates below
are the standard prices; any small-cluster beta trial must be agreed individually.
For clustering,
count all clustered servers, with a minimum of two licensed servers ($590/year).
The free single-server offer applies to standalone use; there is no free first
cluster member. Two-server clusters are supported, with no rigid-quorum
requirement. The clustered price includes unlimited support directly from the
developers for the licence term, without an SLA; the engineer-on-task target is
four hours. Do not add that same included support cost again. Optional tighter
SLAs are quoted separately as an annual fee. Clustering requires active licences
and online validation; air-gapped arrangements require agreement with us.
See the licence terms and payment-lapse behavior at the start of this worksheet.

SynchresisVM item | Amount/formula | Basis | One-time/recurring | Scope
Single-server software | $0 | PRICED | Free forever | Single-server use, including official 1.0
Single-server support during beta | $0 | PRICED | Included period | Throughout closed beta; beta participants keep free support for 90 days after beta ends; no SLA by default
Single-server incident support after beta | ___ hours x $___ = $___ | QUOTE NEEDED | Per incident, billed hourly | All single-server users eligible for a rate below general expert support; beta participants retain their 90-day free support period
Clustered software and expert support | ___ servers (minimum 2) x $295 = $___ per year (minimum $590) | PRICED | Annual | Every cluster member, including the first
White-glove migration | ___ VMs x $15 = $___ | PRICED | One-time | Targets minimal downtime; testing after first boot
Introductory product installation call | $0 | PRICED | Introductory offer | Throughout closed beta and first few months after 1.0; no purchase required

The single-server software remains free forever. The free support period and the
introductory installation offer have the separate durations stated above.
Use the separate
white-glove migration row for workload migration. Keep your own staff time and
other environment-specific costs in the rows below.

Cost item | Amount | Basis/date/source | One-time/recurring | Assumptions
Other software/licenses | ___ | ___ | ___ | ___
Optional annual SLA | ___ | QUOTE NEEDED | Annual | As short as 15 minutes to an experienced VM infrastructure engineer working on your issue during main working hours; optional price-lock contract
Other paid support/services, if needed | ___ | QUOTE NEEDED | As agreed | Avoid counting single-server incident support above twice; free beta support and the participant extension remain included
Hardware/storage/network | ___ | ___ | ___ | ___
Backup/recovery changes | ___ | ___ | ___ | ___
Internal migration labor | ___ | ___ | ___ | ___
Training and operating staff | ___ | ___ | ___ | ___
Parallel operation | ___ | ___ | ___ | ___
Downtime/business impact | ___ | ___ | ___ | ___
Other | ___ | ___ | ___ | ___

Total for comparison period:
Unpriced items/uncertainties:
Sensitivity to workload growth or staffing assumptions:

8. NEXT STEP

What remains unproven:
Who will collect the evidence:
Decision date:
Requirements to discuss with the candidate vendor:

SynchresisVM Server is free forever for single-server use, including the official
1.0 release. Installation calls are a separate introductory offer: free throughout
closed beta and for the first few months after 1.0. No purchase required. You work
directly with the developers. The closed beta is available now.
Book your installation at https://synchresis.net/schedule, or use the beta request
form if you prefer us to get in touch.

Describe your environment and what an evaluation must prove:
https://synchresis.net/synchresisvm-beta