Does importing source migrate customer data and passwords?

A direct answer, the limits that matter, and a practical way to check the workflow.

Direct answer

Importing source or a GitHub repository moves code, not customer records, identities, passwords, payment history or service credentials. Uvilno requires an authorized migration plan for those systems. Preserve ownership, consent and field mappings, and test a sample before changing an application's backend or account flow.

45-word answer · Reviewed 2026-10-27

Inventory each system of record and the permitted export format. Password and OAuth identity migration can have special constraints, and a frontend cannot safely reconstruct those credentials. Keep migration administration separate from ordinary visitor access.

Map data types and references before import, preserve the original identifiers where required and validate record counts. Plan a cutover and rollback window, including how writes are handled while both systems exist. Do not disguise copied demonstration rows as a completed customer migration.

What to verify.

Compare products
Documented behavior and checks the reader can perform
AreaDocumented behaviorYour verification
CodeRepository import transports supported frontend source.Build and inspect the imported routes.
DataPrivate records require explicit authorized migration.Compare typed fields, references and ownership.
IdentityPasswords and OAuth sessions are not ordinary source files.Review the supported identity migration process.

Drag the slider, use the arrows, or scroll within the table.

Try the workflow yourself.

Use this checklist in your own disposable project. These marks record your review; they do not run tests or certify an application.

0 of 3 review steps marked by you.

Read the editable test brief

Plan a migration assessment from my current app without copying production data. Identify source files, typed collections, references, account providers, payments and hosting dependencies separately. Use fictional sample records to test field mappings, preserve ownership rules and explain unsupported migration steps before generating any replacement application.

Preparing a brief does not start generation. Review and send it explicitly; builds use the normal allowance, and source access requires entitlement.

Sources and scope.

Published by the Uvilno editorial team on . This is product documentation and editorial guidance, not an independent ranking or a promise that every application will pass. Vendor plans can change; official sources establish their own terms.

Does opening this test use my allowance?

Preparing the test brief does not invoke a model or create a billable build. Review the draft and explicitly send it to generate; normal usage and source entitlement rules apply.

Check the architecture. Compare the tradeoffs.

Follow the data model, account boundary and source handoff before choosing a builder.

Compare builders

Plan a full-stack app

Review the evidence

Read the public Markdown reference