Curating Content for Migration Walkthrough

Scenario Overview

Many organizations store documents across multiple systems, such as SharePoint sites and shared file systems. Over time, these repositories often accumulate outdated content, and documents that are no longer relevant to business needs. In addition, some content may contain sensitive or personal information that requires careful handling.

When preparing to migrate content into Objective ECM, a simple direct migration approach can introduce risk. Migrating content in its current state can result in cluttered repositories, inconsistent metadata, and sensitive information being exposed to unintended audiences.

This scenario focuses on using Objective 3Sixty to prepare content before migration. Rather than moving everything and cleaning up later, 3Sixty is used to assess, enrich, and curate content while it remains in its original systems, such as Microsoft SharePoint and file systems. Only approved, governed content is then migrated into Objective ECM.

What You Want to Achieve

The goal of this scenario is to migrate content into Objective ECM in a controlled and intentional way. Specifically, you want to:

  • Centralize relevant business content in Objective ECM

  • Exclude outdated or low-value content from migration

  • Identify and protect sensitive or personal information before it is moved

  • Ensure Objective ECM receives trusted, well-prepared content rather than unfiltered source material

By achieving these goals, Objective ECM becomes a high-quality destination for managed content, supporting compliance, discoverability, and long-term governance from the moment content is introduced.

How 3Sixty Supports This Scenario

The following sections describe the conceptual steps involved in preparing and migrating content using Objective 3Sixty. These steps explain what happens at each stage of the process, not the detailed configuration required to perform them.

Objective 3Sixty supports content cleanup and migration by acting as a preparation layer between source systems and Objective ECM. Instead of migrating content first and addressing issues later, 3Sixty allows organizations to understand, and refine, content while it remains in place.

Features Used in This Scenario

This scenario uses several core capabilities within Objective 3Sixty to support content cleanup, governance, and controlled migration into Objective ECM. Each capability plays a specific role in preparing content before it is moved.

Scenario Walkthrough

Step 1. Source System Connections

Connections allow 3Sixty to securely access content stored in source systems such as Microsoft SharePoint and shared file systems. Using configured authentication and permissions, 3Sixty reads content in place without disrupting users or requiring immediate migration.

By establishing these connections, 3Sixty gains visibility into content across systems while day-to-day work continues uninterrupted.

Create the following connections

  • Filesystem Integration and Content Service Connection

  • SharePoint Authentication Integration and Content Service Connections

  • Objective ECM Authentication and Integration Connections

  • OpenSearch Authentication Integration and Content Search Connections

How to Guide:

Connector Configurations

Step 2. Enrich and Analyze Content

Jobs and task group runners are used to execute processing actions. These execution mechanisms support activities such as enrichment, redaction, and preparation steps that must occur before content is approved for migration.

Enrichment capabilities analyze document content and extract meaningful signals. Text extraction and analysis make content searchable and support tagging at scale, allowing organizations to understand what their content contains before making migration decisions.

During enrichment, sensitive or personal information can be identified through tags, enabling organizations to understand where risk exists across large content sets before any content is moved.

Sensitive data handling capabilities identify personal or confidential information within documents. Tagging and redaction can be applied to protect sensitive data, reduce compliance risk, and ensure content is appropriately governed prior to migration.

Analysis Jobs

Create a job for each source connector. These jobs will index and tag content and send the files to Discovery to filter review and process

1. Add the connectors that 3Sixty will use to read, flag, and migrate content.

  • Repository: Filesystem, SharePoint integration connections

  • Output: OpenSearch Integration Connection

  • Content Service: Filesystem and SharePoint Content Service Connections

2. Add the tasks in the following order, as 3Sixty processes tasks sequentially based on their listed order.

  1. Tika Text Extraction will let 3Sixty read the content. This must be the first task listed

  2. PII Detection will flag any files that have sensitive data

  3. Redaction will redact any sensitive information found. Use the transparent redact so you can review the data before redaction

  4. Trivial Detection will flag any content you decide is unnecessary

Migration Jobs

  1. Create a migration job with ECM as the destination. Use either system or SharePoint. This will be the job you use when processing the curated content. Name this something easy to identify in the job drop down like “Clean Migration to ECM”

  2. Add the Redaction Task – use the full redaction to keep sensitive data from being visible

How to Guides:

Connector Configuration

3Sixty Tasks

Step 3. Discover and Assess Existing Content

Discovery enables users to explore indexed content across connected sources. Content views, filters, and reports provide visibility into content volume, age, ownership, and relevance, helping users assess what content should be retained, reviewed, or excluded from migration.

Once sources are connected, 3Sixty provides discovery across all indexed content. Users can explore content volumes, file types, ownership patterns, and other characteristics to assess the overall state of their content.

Through content views, filters, and reports, users can identify outdated materials, and content that may no longer be relevant. This insight supports informed decisions about what content should be migrated and what should be excluded.

Create a content view for 3Sixty Discovery

Create a federated search view

  • Add the Content Service Connector

  • Add users and/or groups that should have access

  • Add the following widgets to the left sidebar section

    • Has PII

    • Obsolete

    • Trivial

How to guides:

Content Views Widgets

Step 4. Curate Content for Migration

Action Curated Content allows users to take curated results from Discovery and initiate further processing. This capability bridges analysis and execution, enabling selected content sets to be sent for cleanup, validation, enrichment, or preparation of workflows.

Using Discovery results, users can curate specific sets of content that are approved for migration. Rather than migrating entire repositories, curated content sets allow organizations to focus on high-value, compliant documents.

Curated content can be sent for further processing using jobs or task group runners, enabling cleanup, validation, or additional enrichment as needed before migration.

Curate new jobs using discovery filters

  1. Filter for PII

  2. Process filtered results

How to guide:

Action Curated Content

Step 5. Migrate Trusted Content into Objective ECM

Migration capabilities move only approved and governed content into Objective ECM. Because content is curated, enriched, and protected in advance, ECM receives trusted content that is ready for long-term management and compliance.

Only content that has been reviewed, enriched, and governed is migrated into Objective ECM. As a result, ECM receives content that is relevant, well-classified, and protected by appropriate access controls.

This approach ensures that Objective ECM starts with a clean, trusted content foundation, reducing ongoing maintenance effort and supporting long-term governance.

Run new migration jobs

How to guide:

Job Runs

Resulting Outcome

By using Objective 3Sixty to prepare content before migration, organizations move only trusted, relevant, and governed content into Objective ECM. Outdated, or low-value material is excluded, and sensitive information is identified and protected before it reaches the destination.

As a result, Objective ECM starts with a clean, well-classified content foundation. Access controls are applied consistently, compliance risks are reduced, and ongoing governance is easier to maintain because content quality and controls are established from the beginning rather than retrofitted later.

When to Use This Approach

  • Content is spread across multiple systems, such as SharePoint sites and file systems

  • There is uncertainty about content quality, relevance, or duplication

  • Sensitive or personal information must be identified and protected before migration

  • Governance and access controls need to be applied prior to introducing content into ECM

  • An organization wants to avoid a large, unfiltered lift-and-shift migration

Using 3Sixty as a preparation and governance layer allows organizations to migrate with intention, ensuring that Objective ECM becomes a trusted system of record rather than a repository of unmanaged legacy content.

Related Links

Jobs Overview

Discovery Widgets