# Migration

---

## Overview

As organizations grow and their IT or R&D infrastructure changes, it may become necessary to migrate the JFrog Platform from a legacy environment to a new deployment, typically on updated or different infrastructure.

This page focuses on migrating Artifactory, the core component of the JFrog Platform and the primary location for storing company binaries.

---

### Migration Considerations

When preparing for a migration, take into account the following key factors:

1. **Data Size:** Total volume of artifacts and metadata.
2. **New Hardware Specifications:** Capabilities and sizing of the target infrastructure.
   - Look into the [Sizing](/self-managed/deployment/sizing) section for details
3. **Scalability:** Ensuring the new environment supports anticipated growth.
4. **Technology Adoption:** Leveraging new technologies or architectures as part of the migration.
   - The recommended platform to install and run the JFrog Platform is Kubernetes. See the [Runtime Platform](/self-managed/deployment/considerations/runtime-platform) section for this
5. **Migration To JFrog SaaS:** There is an easy self service [JFrog Cloud Migration solution](https://docs.jfrog.com/integrations/docs/cli-for-jfrog-cloud-transfer).
   - The benefits of JFrog SaaS are well described in the [JFrog SaaS](/jfrog-saas) section

---

### Migration Process

A successful migration involves moving the following critical components:

1. **Binaries:** Data stored in [Artifactory's filestore](https://docs.jfrog.com/installation/docs/artifactory-filestore).
2. **Database:** Artifactory's internal database, which contains:
   - Binaries Metadata
   - Application and services configurations

For technical details and recommended approaches, refer to the [Artifactory Migration Guide](https://jfrog.com/help/r/comprehensive-guide-to-migrating-jfrog-artifactory/artifactory-migration).