Bring your files.
Keep their history.
A practical plan for moving from spreadsheets, shared folders, or another driver file system.
Start with a small sample
During your introduction, describe your current system, driver count, document formats, and the records you need to keep. Confirm the import method, work involved, any fees, and the proposed timing before authorizing a move.
Bulk migration and a fixed completion date are not included promises in the published base plans. Keep sensitive documents out of the public request form.
A careful migration sequence
- Preserve the original export.
Keep a recoverable copy of documents, driver identifiers, stored dates, and history from your current system.
- Agree on the mapping.
Match each document to the correct driver and record type. Separate issue dates, expiry dates, and review dates.
- Review a sample together.
Compare the uploaded file, its metadata, and its access permissions with the original.
- Reconcile the complete library.
Check expected driver and document counts. Record missing files and exceptions instead of silently skipping them.
- Confirm the handover.
Test document access and downloads. Keep your source archive according to your retention requirements.
What to bring to an introduction
- The number of active and former drivers you manage.
- The current software or folder structure.
- Whether you can export documents and their metadata.
- The people who will maintain files after the move.
Request a 15-minute introduction or compare software options.