Importing Data
Phacility User Documentation (Administrating Instances)

Describes the process for importing data into the Phacility cluster.

Overview

If you have an existing Phabricator instance and you'd like to bring the data into the cluster, we can help import it.

For now, this process is not automated, so you'll need to coordinate with us. This document provides an overview of what to expect and how to move forward.

Import Process

The exact process will depend on how much data you have, how it is stored, and how your current instance is set up. We'll discuss things with you and work out the details when you get in touch.

Before getting started, you should review the Phacility Instance Limitations document to get an idea of things that the cluster doesn't support. If your instance relies on features which we don't support (like running custom code), importing probably isn't a good path forward. (If you aren't sure, feel free to get in touch and we can help answer any questions.)

If you don't rely on any unsupported features, we can move forward with the import process.

First, we'll do a "dry run" import of your data so you can make sure the import goes smoothly and things work properly for you in the cluster. In this phase, your instance will be configured so it doesn't send email or publish events, and your users can continue using your normal install without disruption. You'll be able to evaluate the instance, make sure you're happy with it and that everything is working like you expect, and we can fix any issues which arise.

Once everything looks good, we'll decide on a cutover date when we actually switch users over. You'll give us another dump of your instance and we'll repeat the import process, bringing the cluster instance up to date. We'll disable the silent mode and you'll switch over from your local install to your new cluster instance.

Next Steps

If you're ready to continue:

Defined
src/docs/user/importing.diviner:1