How to report on all Confluence spaces space size - can this display in the Space Directory?

[Nancy Greenfield]

1. Is there any way to see Space Size in Confluence?
2. Is there a way to see the Space Size in the Confluence server management console?
3. Is there a way to see the Space Size from the user or Space Admin side?
4. Can Space Size be displayed in the Space Directory? 
5. Can a report be exported to Excel with the space size, number of attachments and total attachment size and last updated date for each wiki space on Confluence server, to help with management and curation?
6. If we reduce dead weight will it help with eventual migration to the cloud?

[Levente Szabo _Midori_]

If by "space size" you mean the number of pages in a space, you can use the Confluence content health quality feature of Better Content Archiving for Confluence.

It gives you an overview of all your spaces with different metrics for statuses as well as a total. It exists for Confluence Cloud as well, where it's called "Content status overview":

As it was also mentioned, it helps you identify the Confluence pages that are active and read more often, so you know what to migrate to Confluence Cloud. After you migrated, you can recreate the same content status rules for your pages to continue monitoring for activity.

Read more about options for Confluence content quality monitoring and notification >>

(Please note that Better Content Archiving for Confluence is a paid and supported app and I'm part of the team developing it.)

[Nic Brough -Adaptavist-]

What are you thinking of as "size" here?  Number of pages?  Physical volume of uncompressed text in the content?  The space taken up by the line for a page in the database?  Comments?  Attachments? Does the page history count?

Most of those metrics are not really that useful when thinking of a migration though.  What matters more is complexity and the use of apps that might not be as easy to migrate as the raw content.

There is a very simple thing you can do for getting a number that's a comparable "size" though - export a space and look at the size of the file the export is in.  If you export another space and the file is ten times the size, you know the second space is going to take longer to import and take up more space.  (And, of course, you can then use the exports to import the spaces into Cloud as well, actually doing the migration!)

Yes, reducing dead weight makes migration shorter, as there's less to do, but it might not have any impact on the complexity.

Also, identifying the dead weight is harder than it sounds.  You probably don't care about the number of pages in a space, but knowing if those pages are being read...