Skip to main content

Uploadcare migration tool

Project description

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.


This utility requires Python 3.5.

In order to install migro, simply run:

$ pip install uploadcare-migro




<PUBLIC_KEY> — Your Uploadcare project public 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.

-o, --output_file PATH          Path to a Migro output file.
                                [default: migro_result.txt]

--upload_base TEXT              Base URL for uploads.

--from_url_timeout FLOAT        Maximum number of seconds for uploading
                                a single file via `from_url`. If this
                                threshold gets exceeded, a file is
                                considered not loaded. Increase this
                                timeout when expecting to get larger
                                files via `from_url`.
                                [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 format

The 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:

That’s what you get in your Migro output file for those input entries:       success   success       fail        Uploading of these files types is not allowed on your current plan.

How migration works

The 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 the Uploading API. Specifically, it utilizes the From URL method.

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.


Here’s how you run the utility:

$ migro 9a598e2a47fe961ea412 fileslist.txt -output_file /tmp/migro-result.txt

And 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: /tmp/migro-result.txt


You can use our libs to migrate your files from any source.

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Files for uploadcare-migro, version 1.2.1
Filename, size File type Python version Upload date Hashes
Filename, size uploadcare_migro-1.2.1-py2.py3-none-any.whl (12.8 kB) File type Wheel Python version py2.py3 Upload date Hashes View

Supported by

Pingdom Pingdom Monitoring Google Google Object Storage and Download Analytics Sentry Sentry Error logging AWS AWS Cloud computing DataDog DataDog Monitoring Fastly Fastly CDN DigiCert DigiCert EV certificate StatusPage StatusPage Status page