Import a Site or workspace

Preview a prepared workspace export and import its Expressive Markdown into a workspace.

Workspace Admins can import a prepared Knit workspace .zip from Settings → General → Import workspace. Choose the destination workspace first. For just the default workspace, use Default workspace only on Site General while you are in that workspace.

To import a prepared Site ZIP, open Settings → Site → General → Import site. Preview the workspace destinations before committing. The source default workspace goes into the destination's default workspace. Other source workspaces are created when needed, then remembered by their source IDs for later imports. Renaming a destination workspace does not change that mapping. Your Site plan must have room for the proposed workspaces.

No workspace or page is created during preview. On import, links between source workspaces point to the corresponding destination pages. Any remaining drafts across those workspaces share one import session in the usual Drafts view.

The Fellowship

Example workspace

Pages

Journey plans

Journey

Road to Mordor

?
Frodo Baggins
Loading editor…

Try editing a page. Type / for commands. Your changes aren’t saved.

Check From and Into in the preview. Eligible changes publish as new versions. Identical content stays unchanged, and work requiring review remains in drafts.

Preview before importing

  1. Select a prepared workspace export.
  2. Select Preview import. Keep the page open while the archive uploads and Knit checks it. No document changes happen during this check.
  3. Review the source, destination, new and existing document counts, warnings, and What is not restored. Use More documents to inspect later entries.
  4. Open Document details for any conflicts. If an original page is in Trash, choose Restore original or Import as new copy. If it is no longer recoverable, choose Import as new copy. Knit checks the preview again. Correct other stated problems before previewing again. Changes preserved as separate import-conflict drafts can proceed.
  5. Select Import workspace. When it finishes, check the published, unchanged and remaining draft totals. Open a document to inspect the result.
  6. If drafts remain, select View drafts from this import. This opens the usual Drafts view filtered to that session, with its normal review and publishing controls. Clear the session filter to see other drafts.

History, original authorship, approvals, verification, comments and memberships are not restored. Import does not replay historical versions. Pages omitted from the archive are not deleted.

Recover deleted originals

Restore original brings an authorized page back from its normal 30-day Trash window, preserving its identity. Import as new copy leaves the original in Trash and creates a separate page when you commit the import. Later imports remember the copy as their destination. Existing private drafts and access checks still apply. If the destination changes, preview again before importing.

Select Download report in a workspace import for a JSON file listing every document's archive path, disposition and explanation, with the counts and warnings. Knit loads remaining document pages before downloading the report. It excludes document bodies and raw service logs.

Edit the Markdown and import again

Expressive Markdown is the source for imported titles and content. You can edit it and rename a document's file before repacking the archive. Keep its document and source workspace IDs intact, along with the export's manifest and companion files. Packaged assets must retain their integrity information.

Importing again targets the same destination pages. Unchanged published content creates no new version. Eligible changed content publishes a new version using the usual conflict and review checks. Packaged images become destination-owned assets; document links point to the corresponding destination pages.

An existing private draft is preserved. Conflicting incoming content is kept on a separate unpublished page labeled Import conflict, available through View drafts from this import. Required reviews and newer published work can also leave imported changes in drafts for inspection.

Each import groups its remaining drafts in a session, just like other work that creates several drafts together. An import leaves your active writing session and its drafts intact.

Resume or discard

One progress summary stays visible while the archive uploads, its preview is checked, and documents are imported. Finding all documents and assets does not mean validation is finished: destinations and links still need checking. Document progress shows a total only when the import has supplied one; a paged list is not treated as the total archive size. Controls stay steady between automatic steps. Continue preview or Continue import appears when processing needs to be resumed.

The summary and actions sit before Document details. Open those details to read page titles, archive paths, outcomes and problems without losing the overall result. Whole-Site imports use the same progress presentation, with destinations and document details grouped by workspace.

Return to Settings → General → Your imports and select Open import to resume an unfinished session. If an upload is interrupted, choose Continue upload. After a reload, reselect the same archive name and size to resume at the acknowledged position.

Use Continue preview or Continue import if a later step is interrupted. Completed changes remain saved. A preview has an expiry shown with your local timezone; after expiry, preview the archive again.

Older import records may say Detailed results are no longer available after their private details are cleaned up. This is not a zero-document result, and expiration of import details does not remove imported pages. The completed or discarded status remains visible. A Site import cannot show total results when one of its workspace result records is no longer available.

Discard import stops the remaining work and releases its temporary data. Changes already imported remain in the workspace.

Packaged file attachments keep their original bytes and filenames. Knit restores their links in the destination workspace. Each file must fit the 25 MB attachment limit and the destination Site’s remaining storage allowance.

Something unclear or missing on this page? Tell us