Migrate existing files

When you install Sliick Files into an org that already has files, those files are not yet under Sliick management, so they do not appear in the Sliick file list. The Migration tab brings them in: either keeping them on Salesforce, or copying the bytes into whichever external provider you have configured.

Migration runs per source object as an admin batch job. The picker scans your org, shows every object that has files with an approximate count, and lets you select one, several, or all of them. Each selected object becomes its own job, which keeps progress predictable and easy to retry.

For moving one file at a time from a record page instead, see Move files into cloud storage.

Before you start

• Both the Sliick Files Admin and Sliick Files Setup permission sets. The Migration tab and its tooling live in Setup; the base objects and storage configuration live in Admin, so a migration needs both. Without Setup, the tab still appears in the navigation but the page shows an access gate instead of the migration controls.
• An active storage provider configured in Storage Settings. A job snapshots the provider when it is created and will not redirect mid-job.
• Large-file streaming, if you plan to migrate files over about 4 MB. Click Set up large-file streaming in Storage Settings, once a provider is connected. It provisions what the transfer needs for you. Writing it requires the Sliick Files Setup permission set. Entering the per-file Move flow also provisions it, best-effort.

Run a migration

1. Open Storage Setup → Migration → New Job.
2. Click Scan files. A batch walks the org and counts files per object. The list refreshes when it finishes; it polls, so you can wait or re-open. Each row shows the object, an approximate file count, and total bytes. Counts are cached, so next time they are already there. Click Rescan files to refresh them.
3. Tick the objects you want to migrate, or use the header checkbox to select them all. The button shows how many objects and files you have selected.
4. Choose the options. They apply to every selected object’s job:
   • Include Versions - migrate all versions of each file, not just the latest.
   • Delete Originals - after a file is verified, and for images processed, delete the original Salesforce file. It stays recoverable for 15 days in the recycle bin.
   • Stream Large Files - see Migration options and limits.
   • Verify Read-Back - see Migration options and limits.
5. Click Migrate. One job per selected object is created, each in Estimating. Each scopes its object and lands at Ready with exact counts.
6. Review each estimate and click Run. Use Pause and Resume at any time, and Retry Failed to re-run only the failed rows. A retry resumes from saved state, not from the beginning.

The picker counts are approximate; the estimate is authoritative. The scan buckets each file by the record it was first published to, which is a cheap single pass over the org’s files. A file later shared to other records still counts only under its first home, and files uploaded straight to a Library or a user’s personal Files are excluded. The exact in-scope count for an object is computed when that object’s job estimates.

What the estimate reports as skipped

The estimate counts these categories but does not migrate them:

Category	Why
Library-only	The file’s only link is to a Library. It stays in its Salesforce Library tab
Orphan	It has no record link at all
Shared across records	It is linked to more than one business record. Deferred, see Migration options and limits
Provider limit	It is larger than the destination provider’s maximum object size. Rare
Already migrated	A previous job already copied this file to the same provider

Re-running a job is safe. Already-migrated files are skipped, so you never get duplicates. Migrating to a different provider is still allowed.