nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Migration from Oracle DB to Confluence

noemi_anania

I need to migrate an entire Oracle database to Confluence. Will Confluence create a new page for each file present in the database? Is there a limit to the number of pages that can be created? Is there a limit to the number of attachments per page? There are some files in this database that haven't been accessed in a long time and I would like to delete them. Do you recommend deciding which files to delete and which to keep before migration, or can I delete the unwanted files after migrating all of them? Or does it make no difference at all? Thank you!

Accepted answers

Kristian Klima_gtcuat

HI @noemi_anania

With Premium, you're not really limited, in practical terms, by storage capacity, so the number of pages is not an issue.

Generally speaking, after many a migration, migrations are a great opportunity to review and clean up the the content.

I would start with the review in your source - to ensure you have consistency - and remove stuff in the source. The idea is that you work in the environment that you're used to.

Once you migrate your content, you will have to do a review (sanity check) which will be yet another opportunity to fine tune the changes.

Tom_Carrott_Adaptavist

Hey @noemi_anania - your use case sounds interesting!

We're in the early stages of developing a new product that might be relevant to your migration needs. It's called Panorama, and it offers comprehensive content management for Confluence!

If you'd like to learn more, please check out our landing page here - https://www.kolekti.com/getpanorama

Feel free to reach out with any questions!

All comments

Kristian Klima_gtcuat

HI @noemi_anania

With Premium, you're not really limited, in practical terms, by storage capacity, so the number of pages is not an issue.

Generally speaking, after many a migration, migrations are a great opportunity to review and clean up the the content.

I would start with the review in your source - to ensure you have consistency - and remove stuff in the source. The idea is that you work in the environment that you're used to.

Once you migrate your content, you will have to do a review (sanity check) which will be yet another opportunity to fine tune the changes.

Tom_Carrott_Adaptavist

Hey @noemi_anania - your use case sounds interesting!

We're in the early stages of developing a new product that might be relevant to your migration needs. It's called Panorama, and it offers comprehensive content management for Confluence!

If you'd like to learn more, please check out our landing page here - https://www.kolekti.com/getpanorama

Feel free to reach out with any questions!

noemi_anania

Hi @Kristian Klima ,thank you for your response!
Will a new page be created for each Oracle database file?

Kristian Klima_gtcuat

@noemi_anania I don't know what method of migration you're going to use.

I can only presume that one DB file contains a self contained body of content that you plan to migrate to a single Confluence page.

You can, of course, put a file onto a Confluence page as an attachment but Confluence is not designed to be a file repository, it's to show (and collaborate on) the actual content.

noemi_anania

Thank you @Kristian Klima
Which method of migration are possible? Is there detailed documentation available?

Jeffrey Wolfe

Hello,

1. Will Confluence Create a Page for Each File?
Confluence doesn’t have a native feature to directly import Oracle database records as individual pages or files. However, you can use scripts or tools to transform database content into Confluence-compatible formats, such as JSON, CSV, or REST API calls, and automate the creation of pages for each record or file.

2. Limits on Pages and Attachments in Confluence
- Number of Pages. Confluence does not impose a strict limit on the number of pages. However, performance can degrade if your instance becomes overly large without proper structure. Organizing pages into spaces and using labels for categorization is recommended.
While there’s no hard limit on attachments per page, file size restrictions depend on your Confluence instance. Cloud versions often have a 1GB file size limit per attachment. It’s best to avoid adding too many large files to a single page to maintain usability.

Migration manually with CSV format is an option. If you want to save time and reduce errors, consider using third-party tools. I prefer Skyvia for this task. You can find more information about this integration here.

Hope this will be useful

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

cloud

confluence-cloud