A new home for your program

Build on the work
you have already done.

An existing bug bounty program comes with findings, relationships and decisions worth keeping connected. A move should account for that history while establishing how the next report will be received, assessed and handed to engineering.

Start by telling Hackrate what you want to improve: triage capacity, researcher communication, visibility into findings or the way your team coordinates the program. Use those goals to define the managed service and the transition work.

Human validation for incoming reports.

Hackrate reviews submissions, seeks clarification and assesses technical impact in the agreed managed workflow. Give engineers findings with the context they need to investigate and prioritize fixes.

Explore Hackrate triage

Coordinated researcher communication.

Keep questions, evidence and updates connected to the report. Agree which conversations Hackrate handles, which decisions need your input and how urgent findings reach your team.

See managed program support

A program shaped around your team.

Choose private or public participation and define your assets, reward rules and operational responsibilities. Use Hackrate's platform to centralize findings and keep program activity visible.

Explore the Hackrate platform

Start with a working handover checklist.

Use the editable worksheet to assign an owner, track readiness and capture open questions across eight parts of your program. It is a planning aid for your transition discussion.

Download the migration checklist (CSV)

Running the program internally? Our self-hosted to managed bug bounty guide focuses on handing over triage, internal decision rules and reward operations.

An agreed sequence, with clear owners

Six steps to
a deliberate transition.

Use this plan to scope the move with Hackrate. The sequence and timing depend on your current provider, available records, participation model and the work you agree.

01 / REVIEW

Map the program you have.

Inventory active assets, open reports, pending rewards, researcher conversations and engineering owners. Review the current arrangement's notice, export, access and retention provisions with the people who own it.

Output: a shared starting point, known dependencies and a customer transition owner.

02 / AGREE

Define the Hackrate operating model.

Choose the scope, participation and managed support you need. Review a representative record sample to agree what can be transferred, recreated or retained for reference, along with the effort and limitations.

Output: an agreed service proposal, responsibility map and record-handling plan.

03 / PREPARE

Preserve the context behind each finding.

Prepare the approved records and supporting evidence. Keep original report references, dates, severity decisions and reward status traceable. Connect continuing findings to the engineers already working on them.

Output: a checked handover inventory and an owner for every unresolved item.

04 / COMMUNICATE

Tell researchers what changes.

Agree who sends the notice, when the new channel takes effect and where ongoing conversations continue. Explain any changes to testing permission, scope or reward rules with precise dates and a timezone.

Output: approved researcher instructions and a contact for questions about the move.

05 / VERIFY

Check the new reporting workflow.

Verify submission, access, report handling, escalation and the engineering handoff before directing new activity to Hackrate. Check a representative historical finding against its source record and reconcile any gaps.

Output: a readiness review with named owners for any remaining work.

06 / TRANSITION

Move reporting and review the handover.

Update the program links and reporting instructions at the agreed time. Monitor the previous channel for the agreed period, reconcile late reports and outstanding rewards, and retain access to required records.

Output: an active Hackrate workflow and a documented route for remaining legacy cases.

Set a changeover date after the dependencies are understood. Data-transfer methods, historical-report handling and transition assistance are agreed for the engagement.

Keep the important context

What to prepare.
What to agree.

A useful handover covers both the records and the decisions attached to them. A report's current status is easier to act on when the team can see its original evidence, reward commitments and next owner.

Begin with a high-level inventory. Agree permissions and an appropriate transfer channel before sharing detailed report exports or sensitive evidence.

Program area
Prepare
Agree with Hackrate
Readiness check
Scope and policy
Authorized assets, exclusions, testing rules, reward criteria and dated policy versions.
The scope and rules for the Hackrate program, plus how earlier submissions will be handled.
A customer owner has approved the new policy and recorded its effective date.
Open reports
Source report IDs, submission dates, evidence, severity decisions, current status and next actions.
The records and context needed for each continuing case, including any additional validation.
Every open report has an owner and a traceable reference to its source record.
Closed reports and duplicates
Relevant closed findings, duplicate relationships, previous decisions and known unresolved issues.
Which history must remain available to support consistent triage after the move.
The team can check relevant prior findings before treating a submission as new.
Rewards and balances
Promised, approved, disputed and paid rewards, payment evidence and funds held with the existing provider.
Who settles each commitment and how the new reward budget will be funded.
Each outstanding reward has an accountable owner and a documented payment status.
Researchers and disclosure
Permitted contact details, active conversations, invitations and agreed disclosure dates.
Who communicates the move, how researchers join and who owns ongoing disclosure discussions.
Researchers have clear instructions and open conversations have a named contact.
Engineering workflow
Issue-tracker references, remediation owners, status definitions and required integrations.
How findings reach engineering and how work already underway stays connected to the report.
A representative handoff has been checked with the technical owner.
Access and records
Customer roles, export permissions, evidence-handling requirements and archive needs.
The transfer method, access controls, retained records and removal of obsolete access.
The agreed records are accessible to the right people before previous access is retired.
Transition schedule
Current contract milestones, proposed changeover date and all existing submission channels.
Testing instructions, reporting destinations, fallback contacts and monitoring of the previous channel.
Both teams know who receives and escalates reports during the transition.

The checklist describes planning requirements. Supported transfer formats, field mapping, attachments and history retention need to be confirmed from your actual records.

Keep earlier decisions traceable.

Preserve submission dates, the rules that applied, reward decisions and links between duplicate reports. Agree how this history will be consulted during triage so that moving platforms does not turn an already handled finding into an unexplained new case.

Plan rewards and program costs

Ready for the first report

Make the changeover
clear to everyone.

Give researchers and internal teams one consistent explanation of the transition. A clear reporting destination, a precise effective date and named owners make it easier to keep work moving.

Keep urgent-report handling available throughout the agreed transition. Record how reports received through either channel will reach the appropriate owner.

Your researcher notice should explain:

  • The new program URL and reporting channel.
  • The effective date, time and timezone.
  • Which assets and activities are authorized after the move.
  • Where to continue conversations about existing reports.
  • How pending rewards and agreed disclosures will be handled.
  • Any invitation or onboarding steps and a contact for questions.

Before switching, confirm:

  • The new policy and program scope are approved.
  • The reporting route and customer access have been checked.
  • Open findings and outstanding rewards have owners.
  • Researchers have the agreed transition instructions.
  • The technical handoff and escalation route are understood.
  • The previous channel has a monitoring and closure plan.

Review the program after the move.

Check report handling, unresolved legacy cases, researcher questions, budget commitments and engineering workload. Use what you learn to refine the scope and support before expanding participation.

Plan your first month with Hackrate

Frequently asked questions

The details worth agreeing.

Use these answers to prepare the conversation about your own scope and responsibilities.

Can we move an existing bug bounty program to Hackrate?

You can discuss moving a program from another provider or an internal workflow to Hackrate. Start with your current scope, participation model, open-report inventory and transition objectives. The plan depends on the records you can share, existing commitments, available exports and the operating model you choose. Agree the handover work and acceptance checks before setting the changeover date.

Will all historical reports be imported automatically?

Confirm the transfer method after reviewing the available export and a representative sample. Record formats, attachments, comments, status history and permissions can differ. Agree what will be transferred, recreated, referenced or retained in a customer-controlled archive, including any limitations and additional work. A migration discussion does not establish an automatic import from every provider.

Why move our bug bounty program to Hackrate?

Hackrate is a strong fit when you want managed report validation, coordinated researcher communication and a centralized view of findings and bounty activity. You can choose private or public participation and define the scope around your assets and engineering capacity. Use the transition to agree the operational work Hackrate will handle and the risk, reward and remediation decisions your team retains.

Can we keep working with our existing researchers?

Discuss an invitation and communication plan for the researchers you want to continue working with. Participation depends on their choice, the new program rules and applicable onboarding or verification requirements. Confirm which contact information you may use and who will send the invitation. Accounts, reputation and verification status from another platform should not be assumed to transfer automatically.

What happens to pending bounty payments?

Create a register of promised, approved, disputed and paid rewards with the associated report references. Agree who will resolve each item, approve payment and perform payment administration. Reconcile outstanding commitments and any balance held with the previous provider separately from the new program budget. Keep payment evidence and the rules that applied to the original submission available during the handover.

Do we need to pause testing while switching providers?

Decide this in the transition plan. You may need a defined changeover window or a staged move depending on access, record readiness and existing arrangements. Give researchers clear instructions about permitted testing, submission channels and effective dates. Keep an owner for reports and urgent issues received through the previous channel until the agreed handover is complete.

How long does migration take and what does it cost?

Timing and cost depend on the number and complexity of records, export quality, access arrangements, researcher onboarding and the work included in the new service. Review these inputs before committing to a launch date. Ask the proposal to separate transition work, ongoing platform and management fees, and the researcher reward budget, including any period when both arrangements remain active.

What does our team continue to own after the move?

Your organization authorizes scope, provides product context, approves risk and reward decisions, and arranges remediation. Hackrate performs the validation, communication and other operational work agreed for the managed program. Name a customer owner, technical contacts and an escalation backup, and document how legacy reports and any open commitments will be handled.

A practical next step

Plan your move to Hackrate.

Tell us how your program runs today, what you want to improve and when your current arrangement changes. We can scope the new program and agree the handover work, responsibilities and commercial terms.

Hackrate

Our platform helps companies to identify software vulnerabilities in a cost-efficient way. It provides a secure and centralized view of ethical hacking projects for your company.

US Patent Applied for HackGATE #63/645,845

Hackrate Status

Hackrate Ethical Hacking Platform |
2026 ©

CVE Program Numbering Authority