Own Export Migration
Bring your exported archive into a database you control.
Give exported historical data a clear destination. Move authorised records and attachment files into your own database, with a mapping and verification process your team can review.
Understand the export before moving it.
Start with the files your team is authorised to export. Inventory object files, identifiers, relationships and attachments. Keep the original unchanged so the imported result can be checked against it.
Inspect
Review headers, row counts and file hashes.
Map and validate
Define how objects, record IDs and attachment references should be stored.
Import and verify
Retain run reports and compare imported records and bytes with the source export.
Keep the migration reviewable.
Stable export identity and checkpoints support a controlled import. Preserve original text values and verify attachment content. Keep the source service until the destination has been accepted by your team.
Decide how the history will be used next.
A database copy is the foundation for future access. Agree reporting, retrieval and any Viewer integration as a separate part of the project. Export migration does not automatically recreate the original application experience.
Questions, answered.
Does Vivly extract directly from our Own account?
The current utility imports an authorised customer export. Direct Own tenant extraction and native export certification are separate work.
Which destinations are available?
The utility has SQL Server, PostgreSQL, SQLite, Snowflake and MySQL adapters. Validation differs by destination; MySQL live acceptance remains outstanding.
Will imported data immediately appear in Archive Viewer?
No. Migration stores its own dataset. Viewer publication and source-specific mapping need a separately agreed implementation.
Planning an evaluation
Agree the scope before you start.
Own migration is an export-based candidate. A real customer export, its mapping and the selected destination require acceptance before cutover.
Review your migration scope