Microsoft 365 Migration

SharePoint Creative File Migration: Folders or Metadata?

John WilsonJohn Wilson Nov 18, 2026 869 views

Question details

Choose a SharePoint structure for creative files while preserving links between projects and their assets.

SharePoint Creative File Migration: Folders or Metadata?
Product
SharePoint Online, Adobe InDesign, and Adobe After Effects
Device & OS
not provided
Scenario
A creative department is moving years of organized files from an Apple file server to SharePoint.
Observed behavior
The team needs a migration approach that keeps project assets accessible and supports reliable application links.
Before you start

Inventory representative InDesign and After Effects projects, including linked assets stored outside their project folders. Ask IT and the creative team to review SharePoint sync, file names, permissions, and versioning requirements.

Solution 1Recommended

Preserve project folders and test linked assets

Use this approach when creative applications rely on existing folder relationships to locate linked files.

Stable folder relationships are the starting point for migration. SharePoint metadata can help users find files, but it does not repair links inside creative applications.

1
Select pilot projects

Choose several InDesign and After Effects projects with different asset types and folder arrangements, including projects that link to shared assets.

2
Copy the folder structure

Create a pilot document library in SharePoint and copy the selected project folders and their linked assets while preserving their relative folder relationships.

3
Test local access

Open the SharePoint library and select Sync to make the pilot files available through OneDrive. Open the synced projects in InDesign and After Effects and check whether their linked assets resolve.

4
Resolve and document issues

Use the affected application's link or footage controls to identify and relink missing assets. Record any path, naming, permission, or synchronization issues before expanding the migration.

5
Validate with the team

Have IT and creative users open, edit, save, and reopen the pilot projects. Confirm that access, versioning, and the agreed collaboration workflow work as expected before migrating the remaining files.

Preserve project folders and test linked assets
Folder preservation is not a guarantee: Projects may contain absolute paths or links to assets outside the copied folders. Test each representative workflow and plan for relinking where needed.
Free Microsoft Office alternative

Work with Office files alongside your SharePoint migration

WPS Office is a free, lightweight alternative with a familiar interface for working with Office documents as your team migrates. It supports common Microsoft Office formats for a smoother transition, but it does not repair Adobe asset links or replace SharePoint migration testing.

Review migration plans and project inventories in a familiar Office-style interfaceWork with Microsoft Word, Excel, and PowerPoint formats, including DOCX, XLSX, and PPTXUse a free, lightweight Office alternativeContinue working with existing Office files during the transition
QA img-9

Frequently Asked Questions

Should we replace our creative project folders with SharePoint metadata?

Keep the folder relationships needed by linked assets and add metadata for discovery. Metadata does not automatically update links stored in InDesign or After Effects projects.

How can we check whether a migrated project still has its assets?

Sync the pilot SharePoint library through OneDrive, open the project in its creative application, and use the application's link or footage controls to check for missing assets. Save and reopen the project as part of the test.

What if a project links to files outside its project folder?

Include those shared assets in the migration inventory and test their new locations. You may need to relink them in the creative application if the original paths no longer resolve.

How do we make migrated files easier to find in SharePoint?

Use Add column in the document library to create relevant properties, such as client or project, and test library filters and views with pilot files.