Import Page Properties

Bring existing Confluence Page Properties into Simple Metadata with a guided import.

SIMPLE METADATA

Before you begin

  • Access to Simple Metadata app administration.
  • Confluence pages containing Page Properties, and permission to read the pages you want to import. Adding capture macros also requires page-edit permission.
1

Open the import wizard

In the Simple Metadata app, open Schemas → Page Properties. You can also choose Import… and select Page Properties as the source. Review the introduction and continue to Discover.

2

Choose the source pages

Discover existing Page Properties Reports and select the reports you want to import. If there is no suitable report, use the alternative space-and-label option. Discovery respects your Confluence page permissions.

3

Review the proposed schema

Preview schema uses a sample of matching pages to suggest fields. Review the definition and field mapping before continuing, including which fields should be indexed for report filters. The preview is a sample; the background import processes all matching pages, not just those shown in the preview.

4

Confirm and follow progress

Review the selection and optionally add a Simple Metadata capture macro to imported pages. Start the import and follow progress in the wizard or Processes. Each selected report or space-and-label selection creates its own schema and background job. You can close the wizard while work continues.

5

Build a report from the imported data

Review the imported schema and metadata, then add a Simple Metadata Report macro to a Confluence page. Select the new schema, choose columns and configure filters for indexed fields. Pages included in several selected source reports receive a separate entry for each new schema.

What happens to the original pages

Original Page Properties and Page Properties Report macros remain in place. The import copies page data into Simple Metadata; it does not establish ongoing synchronization. Adding capture macros is optional. Package-file import remains a separate workflow that imports schemas only.

If pages are skipped or the import fails

Check progress and job details in Processes. Pages may be skipped when you cannot read them, their Page Properties cannot be parsed, or an entry already exists during a retry. Existing entries are skipped rather than overwritten. If a capture macro cannot be added, check page-edit permission; importing the metadata and placing its macro are separate operations.

Next step: Import and export