Package: uploadcare-migro
Migro helps you migrate to Uploadcare from other cloud file management
services like Filestack, Cloudinary, etc.
Currently, we support migrating from Filestack, but you can migrate
from other services too: you’ll just need to provide your file URLs for import.InstallationThis utility requires Python version 3.8 or later.In order to installmigro, simply run:$pipinstalluploadcare-migroUsage$migro<PUBLIC_KEY><INPUT_FILE>Where:<PUBLIC_KEY>— Your Uploadcare projectpublic key.<INPUT_FILE>— A text file containing a list of file URLs
to be uploaded to your Uploadcare project.Other options:-v, --version               Show utility version and quit.

-h, --help                  Show this help and quit.

--output_file FILE          Path to a Migro output file.  [default:
                            migro_result.txt]

--upload_base TEXT          Base URL for uploads.  [default:
                            https://upload.uploadcare.com/]

--from_url_timeout FLOAT    Number of seconds to wait till the file will be
                            processed by `from_url` upload.  [default: 30]

--max_uploads INTEGER       Maximum number of upload requests running in
                            'parallel'.  [default: 20]

--check_interval FLOAT      Number of seconds in between status check
                            requests.Output file formatThe output file format is quite simple.
For each input file URL or Filestack file handle, there are 3 columns divided by the t symbol (tab).The first column holds input file URL or Filestack handle itself,
second column — upload operation status: success or fail,
third column — output Uploadcare URL or error description.For instance, you’re willing to migrate the three following files to Uploadcare
where the first two are presented as URLs and the third one as Filestack file
handle. Also, that’s how your input text file will then be structured:https://cdn.filestackcontent.com/YBLVVdUpRqC4nOynxDd8
https://www.facebook.com/rsrc.php/v3/y7/r/dTQOHZm7Z-3.svg
uNWvPRXJQmO49MJbPZn9That’s what you get in your Migro output file for those input entries:https://cdn.filestackcontent.com/YBLVVdUpRqC4nOynxDd8       success     https://ucarecdn.com/d8f8de4b-f92e-41a0-b7f9-28fd4baad9ae/
https://www.facebook.com/rsrc.php/v3/y7/r/dTQOHZm7Z-3.svg   success     https://ucarecdn.com/4a03f3d4-2bd3-456e-89a5-008190980248/
https://cdn.filestackcontent.com/uNWvPRXJQmO49MJbPZn9       fail        Uploading of these files types is not allowed on your current plan.How migration worksThe migration itself is fairly simple: you provide a list of file URLs
or Filestack file handlers, and those files get uploaded to your Uploadcare
project. That’s it.
Migro does not download any files. It makes use of theUploading API.
Specifically, it utilizes theFrom URLmethod.As a result, you’ll get a listing of all the uploaded files.
For every processed file, you’re also getting its status and errors,
in case there were any.ExamplesHere’s how you run the utility:$ migro 9a598e2a47fe961ea412 fileslist.txt --output_file /tmp/migro-result.txtAnd that’s what you get:Upload progress: 100%|████████████████████████████████████████████████| 6/6 [00:03<00:00,  1.74s/file]
All files have been processed, output URLs were written to: are here: /tmp/migro_result.txt
Number of failed files: 1
Thanks for your interest in Uploadcare.
Hit us up at help@uploadcare.com in case of any questions.Note for windows usersCurrently there is an issue with program termination by CTRL+C on Windows, so
program can no be terminated correctly by this way.This is a platform dependent python programming language issue.AlternativesYou can use ourlibsto migrate your files from any source.