SourceMigrator

Move your app.
Keep what you built.

Understand what's portable, what's platform-dependent, and what needs investigation before changing the source application.

Analyze an application

The path

  1. AnalyzeAvailable
  2. InventoryAvailable
  3. PlanAvailable
  4. MigrateNot available
  5. ValidateNot available
  6. DeployNot available

Analyze, inventory, and plan are available. Migration, validation, and deploy are not actions yet.

What the later stages mean
  • Migrate. SourceMigrator does not change the application in this release.
  • Validate. Checks against a moved application come later.
  • Deploy. Publishing a replacement is not part of analysis.

What you can learn

Can I move this application?

Start with the evidence. The inventory says what is supported and what is still unknown.

What can be recovered?

Exportable and reproducible items are the parts the evidence says can travel or be rebuilt.

What is tied to the platform?

Platform-dependent items stay marked. SourceMigrator does not pretend they already moved.

What do I do next?

Each analysis ends with a recommended next step. Later stages stay closed until they exist.

What an inventory looks like

A labeled example of the same components a saved analysis uses. It is not your application.

Example application

Source platform
Sample source
Lifecycle
Inventory
Target profile
Not selected

Migration readiness

Blockers
2
Questions
1
Migration
Not performed

Recommended next step

Review the investigation items and capture the missing evidence before any migration planning.

Classification summary

  • Exportable1
  • Reproducible1
  • Platform-dependent1
  • Requires Investigation1

Migration report

The migration report is produced from a saved analysis run. This view does not have one.

Component inventory

Customer list (schema)

A data shape that can travel with the analysis record.

Exportable

High confidence85%

Source: Sample source

Reasoning

The sample shows a simple list of fields. Nothing has been copied into a new database.

Evidence
  • example/customers: name, email

Account screens (application)

Screens that can be rebuilt from the captured description.

Reproducible

Medium confidence60%

Source: Sample source

Reasoning

The behavior is described well enough to rebuild later. It has not been rebuilt.

Evidence
  • Described only. No source files are attached.

Hosted sign-in (authentication)

Sign-in that the current platform operates.

Platform-dependent

High confidence85%

Source: Sample source

Reasoning

The sample depends on the source platform's sign-in. SourceMigrator has not replaced it.

Evidence
  • Declared as platform-hosted. No credentials are included.

Uploaded files (file storage)

Files whose storage location is not in the sample.

Requires Investigation

Low confidence30%

Source: Sample source

Reasoning

The sample does not say where files live, so the inventory does not guess.

Evidence
  • No file location was captured.

Migration plan

This illustration shows a draft per-component plan. Platform-dependent items become a manual checklist. Nothing has been migrated.

Per-component plan

Customer list (schema)

Exportable

Export the captured definition. Workstream: data. Layer: data.

A data shape that can travel with the analysis record.

The sample shows a simple list of fields. Nothing has been copied into a new database.

  1. Copy the captured definition into the target repository.
  2. Keep the evidence locator as the source of truth.
  3. Do not mark this component migrated until a row-count, checksum, or Playwright smoke check passes.

Account screens (application)

Reproducible

Reproduce from captured evidence. Workstream: frontend. Layer: definition.

Screens that can be rebuilt from the captured description.

The behavior is described well enough to rebuild later. It has not been rebuilt.

  1. Recreate this component from the captured evidence.
  2. Do not assume live data or secret values were downloaded.
  3. Re-enter owner-held values on the target.

Hosted sign-in (authentication)

Platform-dependent

Rebuild manually on the target. Workstream: platform. Layer: runtime.

Sign-in that the current platform operates.

The sample depends on the source platform's sign-in. SourceMigrator has not replaced it.

  1. Rebuild this platform-managed capability on the target.
  2. SourceMigrator cannot export the source engine.
  3. Complete the matching manual checklist item before claiming this component moved.

Uploaded files (file storage)

Requires Investigation

Capture missing evidence before planning work. Workstream: data. Layer: unspecified.

Files whose storage location is not in the sample.

The sample does not say where files live, so the inventory does not guess.

  1. Capture the missing evidence named in the finding.
  2. Do not guess the component.
  3. Re-run analysis before assigning export or rebuild work.

Platform-dependent manual checklist

1 open manual task.

Investigation reminders

  • Where are uploaded files stored? The sample names files without a storage location.

Evidence

LabelKindLocatorCaptured
Customer list shape
name, email
Data shapeexample/customersSample text

Blockers

Hosted sign-in stays with the current platform until a replacement is chosen.

Platform-dependent

High confidence85%

Reasoning

Moving the application does not include the platform's sign-in service.

Uploaded files need a location before anyone plans a move.

Requires Investigation

Low confidence30%

Reasoning

The missing location is recorded as a gap, not filled in.

Investigation questions

Where are uploaded files stored?

The sample names files without a storage location.

Analysis run

This illustration shows how an inventory is read. It is not the result of an analysis run.

Application profile resurgenx.saas.next.v1. Health check