Export all your documents from Content Central
Take your document files and their metadata out of Content Central yourself: a built-in bulk download for small sets, and a scripted, resumable export through the transfer service for everything. Works the same whether Content Central is on your server or hosted by Ademero.
Before you begin
- A Content Central account that can search, view, and download every document in scope
- For the scripted export, someone comfortable writing a small program or script
At the end of this guide you'll have your document files on disk, a spreadsheet of their metadata, and a log proving nothing was missed. It's self-service: you need a Content Central account with access to the documents, and nothing from Ademero.
Choose the right method
| Method | Best for | You get |
|---|---|---|
| Bulk download | A limited number of documents you can select in Search or a folder | One ZIP file containing the selected documents |
| Scripted export | All documents, large collections, runs you can resume, and exports that need an audit trail | A folder tree of document files, plus a CSV or XLS manifest and a verification log |
Both methods work the same whether Content Central runs on your own server or is hosted by Ademero.
Before you begin
- Use a dedicated Content Central account with access to every catalog and document type you're exporting. The export never bypasses permissions, so a full administrator with access to everything can complete the whole export alone.
- Confirm that account can search, view, and download the documents.
- Pick a destination with enough free space for the files, the ZIPs, the manifest, and temporary files.
- Decide the scope. Both methods retrieve the current stored document.
Prior versions, deleted items, annotations, audit events, and workflow history are separate data and aren't part of the document-file export. If you need any of them, plan that before you start.
Method 1: built-in bulk download
Sign in with the export account and open Search or the folder you want.
Limit the results to a manageable batch, then select the documents to export.
Choose Download.
What you should see: Content Central prepares one ZIP file containing the selected documents.
Save the ZIP, extract it, and repeat until every result set is done.
If your browser, proxy, or workstation struggles with a large ZIP, use smaller batches. Keep a simple log of which batch covered what, so a failed or repeated batch is easy to spot.
To take the field values along, click Export CSV on the same search results. Export documents and their metadata covers that export.
Method 2: scripted, resumable export
A complete export is safest in two stages: first create a manifest that lists every document, then download every document named in it. Keeping the list separate from the transfer makes the run easy to resume and easy to verify.
Stage A: create the manifest
Go to Administration > Report Templates and create a report that covers the catalogs and document types in scope.
Include at least these system fields: Document ID, Catalog, Document Type, Document Filename, Document Folder, Document Version, Document Creation Date, and Document Modified Date. Add any business fields you need outside Content Central.
Generate the report and download it as CSV or XLS. Set Write mode: to
ReplaceorKeepAllso the result is one complete, identifiable file.Check the manifest for the counts, catalogs, and document types you expect. Keep the original unchanged; it is the control file for the rest of the export.
Stage B: retrieve each document
Content Central exposes a SOAP transfer service under the same address your users sign in at:
| Purpose | Address |
|---|---|
| Transfer service | https://<site>/<ContentCentral-path>/Services/2010/01/01/CCTransferService.svc |
| Service description (WSDL) | https://<site>/<ContentCentral-path>/Services/2010/01/01/CCTransferService.svc?wsdl |
Generate a SOAP client from the WSDL. Use HTTPS, MTOM message encoding, streamed transfer, and timeouts long enough for large files.
Send a RequesterCredentials SOAP header containing
Domain,Username, andPassword. The header namespace ishttp://www.ademero.com/services/ContentCentral/DataContracts/2010/01/01/.Call GetAuthenticatedUserId once and keep the user ID it returns.
For each Document ID in the manifest, call DownloadDocument with the Document ID and the user ID. Save the returned stream under the returned filename.
Record the result for every row:
Success,NoPermission,NotFound, or the error received. Retry transient failures after a delay, and never silently skip a row.
To avoid filename collisions, write each file beneath Catalog / Document Type / Document ID / returned filename. Clean up characters your file system doesn't allow, but keep the original names in the manifest.
Implementation outline
This C# outline shows the client settings and the call order. Add a Service Reference, or use another SOAP client generator, for the real proxy and message types; generated type names vary by tool.
var binding = new BasicHttpBinding(BasicHttpSecurityMode.Transport) {
MessageEncoding = WSMessageEncoding.Mtom,
TransferMode = TransferMode.Streamed,
MaxReceivedMessageSize = long.MaxValue,
ReceiveTimeout = TimeSpan.FromHours(24)
};
var client = new CCTransferServiceClient(binding,
new EndpointAddress(transferServiceUrl));
using (new OperationContextScope(client.InnerChannel)) {
var credentials = new RequesterCredentials {
Domain = domain, Username = username, Password = password
};
var header = MessageHeader.CreateHeader(
"RequesterCredentials", credentialsNamespace, credentials);
OperationContext.Current.OutgoingMessageHeaders.Add(header);
Guid userId = client.GetAuthenticatedUserId(
new GetAuthenticatedUserIdRequest()).Id;
foreach (Guid documentId in documentIds) {
var response = client.DownloadDocument(
new DownloadDocumentRequest(documentId, userId));
// Require Result == Success, then copy response.Data to a file.
// Log the document ID, returned name, byte count, and SHA-256.
}
}Verify the export
- Counts match. Attempted, successful, failed, and skipped counts add up to the manifest's row count.
- Every success is logged with its Document ID, returned filename, byte length, destination path, and a SHA-256 checksum.
- Every
NoPermissionandNotFoundis explained. Fix the account's access or confirm the document's state, then rerun only those rows. - A sample opens. Open documents from every catalog and document type, including large files and unusual formats.
- The paperwork travels with the files. Store the original manifest, the final result log, the checksum list, and a note describing your folder naming alongside the export.
The export folder holds your documents outside Content Central's security, and the script holds a password. Protect both according to your organization's security and retention rules, and delete temporary files once the export is accepted.
Still stuck?
If a bulk download fails or the transfer service won't respond, contact Ademero support with: which method you used, the catalog and document type in scope, the expected count versus what you got, the exact message or result code, and the date and time of the attempt.
Want Ademero to do it for you?
If you don't have people to run this, or would rather we handle it, Ademero is happy to do the export for you as a professional-services engagement, including help loading it into whatever comes next. That's a convenience to save you time, never a requirement. Contact our solutions team at solutions@ademero.com, and tell us roughly how many documents you have and your target date.
