Summary
Add support for importing and exporting Base (Bitable) as a .base archive file.
Motivation
For Base users, a native archive format would make it much easier to:
- migrate a Base between environments or workspaces
- create full-fidelity backups
- share reusable Base templates
- restore a Base without manually recreating tables, fields, views, and data
Current import scenarios like CSV/Excel only cover part of the use case. A .base archive format would be a better fit for full Base portability.
Proposed Capability
Support both directions:
- export an existing Base to a
.base archive file
- import a
.base archive file to create or restore a Base
Expected Scope
Ideally the archive can preserve as much Base structure as possible, for example:
- tables
- fields and field configuration
- views
- records
- relationships / linked fields when possible
- basic metadata needed to reconstruct the Base
Possible CLI UX
Examples:
lark-cli base export --base-token= --format=base | xlsx | csv --output archive.base
lark-cli base import --input archive.base
Why This Matters
This would make the CLI much more useful for backup, migration, environment sync, and template distribution workflows around Base.
Thanks for considering this feature.
Summary
Add support for importing and exporting Base (Bitable) as a
.basearchive file.Motivation
For Base users, a native archive format would make it much easier to:
Current import scenarios like CSV/Excel only cover part of the use case. A
.basearchive format would be a better fit for full Base portability.Proposed Capability
Support both directions:
.basearchive file.basearchive file to create or restore a BaseExpected Scope
Ideally the archive can preserve as much Base structure as possible, for example:
Possible CLI UX
Examples:
Why This Matters
This would make the CLI much more useful for backup, migration, environment sync, and template distribution workflows around Base.
Thanks for considering this feature.