When importing a Confluence space, attachments are restored and receive new IDs/URLs in the target site/space, but inline attachment links and images in page content still reference the old URLs. The space import flow does not rewrite those URLs to point to the imported attachments, resulting in broken or cross-site links after import.

Current behavior
Export a space from Site A and import it into Site B.

Attachments are imported into the new space and are accessible via their new URLs.

Pages that contained links or images pointing to attachments by URL still store the original URLs in their storage format.

After import, those links continue to point to the old site/space/attachment and may be broken or undesired.

Expected behavior

During space import, Confluence should detect internal attachment links in page storage that belong to the imported space and update those URLs to refer to the newly imported attachments/paths in the target space.

Impact

Imported spaces can contain many broken or cross-instance attachment links, especially in documentation-heavy spaces that use direct attachment URLs.

Customers have to manually reinsert attachments on pages or build custom scripts to rewrite the links after import.

Workarounds

Manually re-insert attachments on affected pages via the editor, using the attachment/file picker.

Use REST API / scripts to fetch page storage, perform string replacements for old base URLs/paths, and update the pages.