Import and migration

Import reads content from Git, GitHub, GitLab or SVN and converts it into a DigiVC repository. Git/SVN are not the DigiVC engine; they are migration source connectors.

Preparation

• Create or select a target project.
• Confirm that server import capabilities report an available Git or SVN runtime.
• Check free storage space.
• Decide whether full history or only the latest snapshot is required.

New import

Open Administration → Import / Migration and enter:

• source type;
• source URL;
• branch/ref;
• target project;
• repository code and name;
• DigiVC default branch;
• history mode;
• maximum source revisions;
• visibility and access-request policy.

Private source

You may provide a username and access token/password. Credentials are used only in worker memory for the current job and must not appear in the URL, job record, logs or evidence.

TLS verification

Keep Verify TLS enabled. Disable it only for a controlled internal source that you explicitly trust.

Full history or snapshot

• Full linear history — creates DigiVC revisions for source history up to the configured limit;
• Latest snapshot only — imports only the latest content.

For full history DigiVC stores a mapping between source revisions and DigiVC revisions, including a SHA-256 digest.

Example: GitLab import

Source type: GitLab
Source URL: https://gitlab.example/erp/server.git
Source ref: main
Target project: ERP
Repository code: server-migrated
History mode: Full linear history
Verify TLS: Yes

Cancellation

When cancelled, a partially created repository is archived. It is not presented as a successful migration.

After completion

1. Open the target repository.
2. Review the tree and history.
3. Review the mapping digest.
4. Grant permissions to the correct groups.
5. Perform a test checkout with the Desktop Client.