https://github.com/perforce/p4transfer

[Community Supported] Utility for transferring a subset of files (with complete history of all changelists) from one Helix Core repository to another, only requiring read access to the source repository.
https://github.com/perforce/p4transfer

Last synced: 6 days ago
JSON representation

[Community Supported] Utility for transferring a subset of files (with complete history of all changelists) from one Helix Core repository to another, only requiring read access to the source repository.

• Host: GitHub
• URL: https://github.com/perforce/p4transfer
• Owner: perforce
• License: bsd-2-clause
• Created: 2021-01-29T17:23:49.000Z (about 5 years ago)
• Default Branch: main
• Last Pushed: 2025-08-20T15:31:52.000Z (6 months ago)
• Last Synced: 2025-08-20T17:41:20.236Z (6 months ago)
• Language: Python
• Homepage:
• Size: 1.02 MB
• Stars: 52
• Watchers: 13
• Forks: 21
• Open Issues: 25
• Metadata Files:
  • Readme: README.md
  • License: LICENSE
  • Code of conduct: CODE_OF_CONDUCT.md

Awesome Lists containing this project

README

          
![Support](https://img.shields.io/badge/Support-Community-yellow.svg)

# p4transfer

Utility for transferring a subset of files (with complete history of all changelists) from one Helix Core repository to another, only requiring read access to the source repository.

## Overview

The script `P4Transfer.py` is for use when transferring changes between two Perforce Servers (one way).

## Requirements

This requires Python (2.7 or 3.6+) and P4Python (2017.2+). It runs on Linux/Mac/Windows.

Also for other modules:

    pip install -r requirements.txt

If you have problems with the above, check the doc below.

## Documentation

See [doc/P4Transfer.adoc](doc/P4Transfer.adoc) for more details on how it works and how to use it. You can also download [P4Transfer.pdf](doc/P4Transfer.pdf)

This includes:

*   When to use p4d-native P4DVCS commands instead of P4Transfer

*   Detailed configuration and usage

*   How to ask for support

## Support

P4Transfer is a community supported project and is not officially supported by Perforce.

Pull requests and issues are the responsibility of the project's moderator(s); this may be a vetted individual or team with members outside of the Perforce organization.

Perforce does not officially support these projects, therefore all issues should be reported and managed via GitHub (not via Perforce's standard support process).

## Build/Usage

See Documentation link above.

## Contributer's Guide

See Documentation link above.