SharePoint Online document libraries
You can copy the contents of document libraries from Microsoft SharePoint Online to personal Yandex Disks of Yandex 360 for Business users.
Terms and limitations
From how many libraries can I copy libraries at a time?
-
Within one migration, you can specify up to 20,000 employee usernames, with each username corresponding to only one SharePoint library.
If you need to copy several libraries to one Yandex Disk, perform multiple migrations. They need to be run sequentially: the copying of each subsequent library should only start after the previous library has been fully copied.
Where are the files copied to?
-
During migration, a separate folder is created on the user's Yandex Disk. The structure of subfolders and files is preserved.
Folder naming and pathing
Each document library has a unique URL. It contains:
-
Tenant name (
tenantname
in the example below). -
Family of sites (
sites
in the example below). -
Site name (
examplesite
in the example below). -
Subsite name, if any (
subsite
in the example below). -
Name of the document library (
Shared%20Documents
in the example below).
These items form a hierarchy of subfolders on Yandex Disk. For example, if the path to the document library looks like
https://tenantname.sharepoint.com/sites/examplesite/subsite/Shared%20Documents
, then the subfolder structure on Yandex Disk will be as follows:http://disk.yandex.ru/client/disk/tenantname/sites/examplesite/subsite/Shared%20Documents
.If you use the document library in the root site (
root
), it will be copied to a folder that looks like this:http://disk.yandex.ru/client/disk/tenantname/root/root/Shared%20Documents
. -
File copying limitations
- For successful migration, the file name length in the library must not exceed 255 characters. Files that don't meet this condition won't be copied. Before migrating, check the contents of the SharePoint library for such files and rename them.
Start migration
-
Prepare a secret, link a domain, and prepare employee accounts if you haven't already done so.
Note
The secret applies to all running migrations. If you have already started migration and then upload a new secret, it will be applied to this migration. The secret permissions are also taken into account: if the new secret only has access to files and you have started email migration, it will stop.
-
Select where you want to migrate files from: click Microsoft 365.
-
Upload the secret file and click Next.
-
Specify the accounts to whose Yandex Disks you need to migrate document libraries, along with the links to these libraries:
-
Download the CSV file template.
-
Follow the template to add the usernames of Yandex 360 for Business users and the URLs of the migrated document libraries to the file.
The first line of the file is the field headers — don't delete it. Each subsequent line of the file should have the following items specified:
-
Username of the Yandex 360 for Business user who owns the personal Yandex Disk. Usernames shouldn't repeat within the same file.
-
URL of the Microsoft SharePoint Online document library.
For example, to copy a document library with the URL
https://tenantname.sharepoint.com/sites/examplesite/subsite/Shared%20Documents
to the personal Yandex Disk of the Yandex 360 for Business useri.ivanov@example.test
, specifyi.ivanov
in theyandex_login
column and the specified URL in thedrive_id
column.The resulting file should have the following structure:
"yandex_login";"drive_id" "i.ivanov";"https://tenantname.sharepoint.com/sites/examplesite/subsite/Shared%20Documents"
Note
You can specify up to 20,000 usernames in one CSV file. You can't specify the same usernames in one file. Copying the libraries specified in one file is launched in parallel.
-
-
Save the CSV file in UTF-8 encoding (in Microsoft Excel, click Save as → CSV-UTF8).
Alert
If you save the file in a different encoding, it won't be recognized correctly.
-
Click Upload CSV and select your file.
-
-
Click Start migration.
Data collection takes from a few minutes to two hours, and then the files start appearing on Yandex Disk. If some of the files are already on Yandex Disk (for example, they were moved earlier), the dates when they were last changed in SharePoint Online and Yandex Disk are compared, and the older versions are replaced with the newer ones.
After the copying is complete, the files are no longer synchronized. If new files appeared in the SharePoint library after the copying is completed and you want to migrate them to Yandex Disk, start a new migration.
Once migration is complete, make sure that the number of copied files is the same as the number of files in the source. If you plan to run the process multiple times, save the migration report before each new run. If errors occur during migration, you'll be able to track at which run they appeared.
Where can I view the migration report?
To download the report, go to the active migration page and click Details in the top-right corner. The report displays the logs of the last launched migration process. They contain detailed information about the number of files copied to the personal Yandex Disk and any errors that occurred during this process.
What happens if I stop migration?
All running migrations will be stopped. Any files already copied at the time of the stop will be saved.
What happens if you start a new migration
If you start a new migration before completing the previous one, the new migration will run in parallel with the already launched process for all personal Yandex Disks.
Alert
If you want to run a migration with a file that contains a username involved in another active migration process, you'll need to wait for the first migration to complete. You can view the progress status in the details.
Troubleshooting
You can view a detailed description of migration errors in the migration report. For ways to fix these errors, see Migration error report.
A data format in which values are separated by delimiters (usually commas, but other delimiters can be used as well). It's usually used for storing tabular data and exchanging information between different systems.
A commonly accepted and standardized text encoding that allows storing Unicode characters. Widely used in operating systems and the web space.