S
Simpleasyty
Help Center — Import Page Properties
GETTING STARTED
IntroductionQuick start
CREATE A SCHEMA
Create a schema from a templateCreate a schema from scratch
SCHEMA TEMPLATES
Security Risk RegisterISO 27001 Document ControlSOC 2 Evidence RegisterPolicy ManagementThird-Party RiskData ClassificationApplication PortfolioControlled DocumentArchitecture Decision RecordInformation Asset RegisterBusiness Continuity RegisterGDPR Processing Activity
IMPORT
Import a JSON or YAML schema packageImport Page Properties
FIELD TYPES
Schema field typesText fieldsNumber fieldsYes / No fieldsSingle choice fieldsDate / Time fieldsEmail fieldsURL fieldsConfluence reference fieldsList fieldsField group fields
MANAGE SCHEMAS
Manage schemasIndexed fields and filtersSchema permissions
CAPTURE DATA ON PAGES
Capture metadata on a pageCapture, validate and repair metadata
CREATE REPORTS
Build a Metadata ReportConfigure report filters and viewer controls
STORAGE & PRIVACY
Data residencyStorage in ForgeRetention and deletion
COMPLIANCE
Compliance workflowsMetadata, history and revisions
ADMINISTRATION & TROUBLESHOOTING
Import and exportSchema reconciliation and processesSecurity, storage and limitsTroubleshoot schemas, filters and reports

IMPORT

Import Page Properties

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

Before you begin

Check these requirements before following the steps below.

  • 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. 1

    Open the import wizard

    In the Simple Metadata app, open Schemas → Import and choose Page Properties as the source. Continue to Discover.

  2. 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. If a recently created report is missing, wait for Confluence to index it and try again.

  3. 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. 4

    Review permissions for the new schema

    Choose the spaces, page labels and contributor groups that may use the imported schema. The source space and label only select pages to import; they do not automatically restrict the new schema. Leave a permission empty to allow all values for that setting. Review any selected restrictions again on Confirm import.

  5. 5

    Confirm and follow progress

    Review the selection and optionally add a Simple Metadata capture macro to imported pages. New macros are placed at the top of each page by default; choose Bottom of page if preferred. Start the import and follow progress in the wizard or Processes. The page total counts each matching page once; macro placement has its own live progress. Each selected report or space-and-label selection creates its own schema and background job. You can close the wizard while work continues.

  6. 6

    Build a report from the imported data

    When the job finishes, review the final report for imported, skipped and failed page counts. Open Processes to inspect page-level outcomes and reasons, and retry failed macro placements when needed, before treating an incomplete import as finished. 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 metadata 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 metadata already existss during a retry. Existing metadata is 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.