# Uploading 17500 users and their avatars using PHP

**URL:** <https://meta.discourse.org/t/uploading-17500-users-and-their-avatars-using-php/71685>\
**Category:** Development\
**Created:** [09.Октябрь.2017 14:39:06 UTC](https://meta.discourse.org/t/uploading-17500-users-and-their-avatars-using-php/71685 "2017-10-09T14:39:06Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![DeanMarkTaylor](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/deanmarktaylor/32/102462_2.png) [@DeanMarkTaylor](https://meta.discourse.org/u/DeanMarkTaylor)\
**Post date:** [09.Октябрь.2017 15:10:01 UTC](https://meta.discourse.org/t/uploading-17500-users-and-their-avatars-using-php/71685/7 "2017-10-09T15:10:01Z")

</div>

> [@Frank\_Bailey](#):
>
> So I can do the import to a local Discourse instance and then restore that to the production version?

Yes, restoring a backup does this.

> [@Frank\_Bailey](#):
>
> Will the restore override the settings on the production version?

Yes, except for those settings in your `app.yml` / configuration file - the backup will be restored as it has been backed up.

> [@Frank\_Bailey](#):
>
> If so then this won’t be viable as loads of configuration has been done on the production version.

I believe you could (not done this myself)…

1. backup your existing production Discourse instance.
2. restore to the development instance.
3. process import.
4. backup dev
5. restore to production.

Keep in mind depending on your DB size etc you import can take some time.

---

_[View the full topic](https://meta.discourse.org/t/uploading-17500-users-and-their-avatars-using-php/71685)._