Import and export Redis data
Understand the current Redis data paths: inspect values, copy commands and use server-side migration tools deliberately.
Tablyne’s Redis workflow is centered on keyspace inspection, staged edits and the command console. It does not present a generic import wizard or a database-wide export button. Copying a visible value is not the same as backing up a Redis deployment.
The key inspector can read strings, hashes, lists, sets, sorted sets and streams in bounded portions. It preserves non-UTF-8 values as bytes and can display a value in text, JSON-like text or hexadecimal form when the content allows it. The command log, Commands the Tablyne sent, can copy an individual command, but it is not a dump of the server state.
For migration or backup, use Redis or Valkey’s own RDB, AOF, replication or provider-specific tools according to the deployment. Commands that are destructive, administrative or opaque remain subject to classification and confirmation in the console. A dump operation should be planned separately from a key edit and should be validated on a destination before replacement.
If a file or stream is converted into Redis commands, review the generated commands, limit the batch and choose the target database explicitly. Never treat an unverified bulk script as a harmless read.