IMPORT, EXPORT AND PORTABILITY
Easy to move in. Free to move on.Easy to move in. Free to move on.
Bring files from S3-compatible storage. Retrieve original files when you need them. Keep your options open.
Your files, in their original formats
Existing storage → Keldra → Your chosen destination
IMPORT
Bring existing files with you
Move customer files from S3-compatible storage, keep the originals and verify the transfer before switching applications.
1
Inventory your data
List source buckets, object counts, bytes and versions. Identify metadata and retention settings that must survive the move.
2
Check source access and transfer costs
Confirm credentials and permissions. Check the source provider’s download charges and any restrictions on export.
3
Create destination buckets
Create private buckets in the correct customer service and configure access rules before copying data.
4
Configure indexing where required
Create the index definitions for supported data before import so incoming records can be indexed as they arrive.
5
Transfer original files
Use S3-compatible tools to copy originals. Preserve needed content types and custom metadata; copy retained historical versions explicitly.
6
Compare and verify
Compare counts and bytes. Download sample files and compare their contents or checksums. Confirm application reads, writes and searches.
7
Plan ongoing changes and cutover
Arrange a final sync or write pause, update endpoints and credentials, and retain a rollback copy until the application is verified.
Include versions and metadata you need to keep. A normal sync of current objects does not migrate every historical version or permission rule.
EXPORT
Leave with the files you uploaded
Retrieve original customer files and move them to another S3-compatible destination. No proprietary conversion is required to recover the uploaded bytes.
1
Choose the destination
Confirm its capacity, credentials, object-key support and permissions. Check any destination limits before starting.
2
Export original objects
Use S3-compatible tools to download or copy originals. Include historical versions separately when they must be retained.
3
Preserve required metadata
Carry over content types and custom metadata. Verify the chosen transfer tool preserves the metadata your applications depend on.
4
Verify the export
Compare object counts, bytes and file contents or checksums with the Keldra source. Test representative application operations.
5
Update your applications
Plan a final sync, update endpoints and credentials, then check reads and writes against the destination.
6
Recreate access and index settings
Application permissions and index definitions are separate from original files. Recreate them in the destination where needed.
7
Remove source data after verification
Keep a rollback window and required backups. Delete source data only after the export and application cutover are verified.
aws --profile keldra --endpoint-url "$S3_ENDPOINT" \
s3 sync "s3://$BUCKET/" ./export/
JSON stays JSON. Video stays video.
Export the original files customers stored, not a proprietary replacement for them. Index definitions and application access rules remain separate configuration.
JSON
Retrieve the JSON document originally uploaded.
Video
Download the video file in its original format.
Every other original
Keep your uploaded file format when moving elsewhere.
JSON
Retrieve the JSON document originally uploaded.
Video
Download the video file in its original format.
Every other original
Keep your uploaded file format when moving elsewhere.
JSON
Retrieve the JSON document originally uploaded.
Video
Download the video file in its original format.
Every other original
Keep your uploaded file format when moving elsewhere.
Step-by-step help
Start with one file, verify it, then apply the same discipline to a larger migration.
Plan a bucket migration
Prepare credentials, versions, metadata and destination access before copying files.
Verify a transfer
Download your first uploaded file and check that the bytes match.
Export your files
Download originals with the AWS CLI and verify them before retiring the source.
Plan a bucket migration
Prepare credentials, versions, metadata and destination access before copying files.
Verify a transfer
Download your first uploaded file and check that the bytes match.
Export your files
Download originals with the AWS CLI and verify them before retiring the source.
Plan a bucket migration
Prepare credentials, versions, metadata and destination access before copying files.
Verify a transfer
Download your first uploaded file and check that the bytes match.
Export your files
Download originals with the AWS CLI and verify them before retiring the source.
Frequently asked questions
Keep the original files and plan separately for versions, permissions and indexing configuration.
Which tools can import or export files?
Use an S3-compatible tool such as AWS CLI, rclone or a compatible SDK. Configure the regional endpoint and the appropriate source and destination credentials.
What is the difference between indexed data and original files?
Original objects retain their uploaded file formats. Indexes make supported records searchable, but exporting an original does not bundle its index definitions or application permission configuration.
How do I verify a transfer?
Compare object counts and bytes, then compare file contents or checksums on a representative sample or the full dataset. Test application access before switching production traffic.
How do I migrate safely?
Check source transfer charges and destination permissions. Plan for ongoing writes and a final sync, keep a rollback copy and verify the destination before removing source data.