Documentation

Importing & Exporting

View as Markdown

In Clear Ideas, archives help with both import and portability. You can upload and unzip ZIP files to add structured content to a site. Site export snapshots are managed separately from Site Settings > Export.

Uploading and Unzipping a Zip File

Users can manage archives by uploading Zip files to a site and utilizing the "Request Unzip" feature. This process efficiently organizes and integrates the files and folders contained in the Zip file into the designated site. This method is ideal for importing structured data swiftly and maintaining organizational consistency within the platform.

Supported Formats

Supported Formats:

  • ZIP - .zip (application/zip)

Uploading a Zip File

To upload and unzip a Zip file:

  1. Navigate to the site where you want to import content
  2. Upload the Zip file like any other file
  3. Once uploaded, use the "Request Unzip" feature to extract contents
  4. Files and folders from the Zip are organized and integrated into the site

Process: The unzip process extracts all files and folders from the Zip archive while preserving the folder structure.

Use Cases:

  • Importing bulk documents
  • Migrating content from other systems
  • Restoring backups
  • Adding pre-organized content structures

Site Exports

Site exports now use first-class export jobs and schedules rather than creating an export folder in the site.

From Site Settings > Export, administrators can:

  • create an on-demand export job
  • track pending, running, completed, failed, and canceled export jobs
  • refresh the export job list without refreshing the browser
  • download completed export ZIP artifacts
  • delete export artifacts when policy allows
  • create scheduled exports with retention days

See Site Exports for the complete export and scheduled export workflow.

Export Processing Time

Small Sites: Typically complete within minutes

Large Sites: May take longer depending on content volume

Background Processing: Exports are processed asynchronously, so you can continue working while the export is being created

Use Cases

Backup and Archival

Regular Backups: Use scheduled exports to create recurring snapshots of important content

Project Completion: Export sites when projects are completed for archival purposes

Compliance: Maintain exports for compliance and record-keeping requirements

Offline Access

Local Copies: Download exports to access content offline or on local networks

Portable Archives: Share exported zip files with team members who need offline access

Disaster Recovery: Keep exports as part of disaster recovery planning

Migration and Transfer

Content Migration: Use exports to transfer content between accounts or systems

Data Portability: Maintain portable copies of your data for flexibility

System Transitions: Export content when transitioning between systems

Best Practices

Regular Exports

Schedule: Export important sites regularly to maintain current backups

Before Changes: Export sites before making significant structural changes

Milestones: Export sites at project milestones for historical records

Export Management

Organization: Keep track of export dates and purposes

Storage: Store exported zip files in secure, accessible locations

Versioning: Consider dating or versioning exports for better organization

File Size Considerations

Large Sites: Be aware that exports of large sites may result in large zip files

Download Time: Large exports may take time to download depending on your connection

Storage Space: Ensure you have sufficient storage space for exported files

Limitations

Export Frequency

On-Demand and Scheduled: Exports can be created manually or by a schedule

Multiple Exports: Multiple exports can be requested, but each processes separately

Concurrent Limits: There may be limits on concurrent exports

Content Scope

Site Contents Only: Exports include site contents only

Settings Excluded: Site settings, user permissions, and configurations are not included

Current State: Exports reflect the current state at the time of export, not historical versions