Skip to content
Skillpedia
Databases40k · #5091

creating-oracle-to-postgres-master-migration-plan

Helps your agent plan data migration from Oracle to PostgreSQL. It identifies suitable projects and creates a detailed migration plan.

What it does

This tool examines a .NET software project to identify which parts need to be converted from an Oracle database to PostgreSQL. It then organizes this information into a plan.

When to use it

  • ✓When starting a multi-project Oracle to PostgreSQL migration.
  • ✓When you need an inventory of which projects use Oracle.
  • ✓To assess which .NET projects have Oracle dependencies.

Example of what to ask your AI

“Analyze my .NET solution and create an Oracle to PostgreSQL migration plan.”

Want more? Open the sections below.

How to use

The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.

Skill link

https://github.com/github/awesome-copilot/blob/main/skills/creating-oracle-to-postgres-master-migration-plan/SKILL.md

Ready-to-paste message

Use this skill to help me: https://github.com/github/awesome-copilot/blob/main/skills/creating-oracle-to-postgres-master-migration-plan/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.
How it works

The tool finds your main project file (.sln), lists all other projects, and checks each one for signs of Oracle usage. It then classifies each project as 'needs migration', 'can skip', 'already migrated', or 'test project' and generates a report.

Installation

Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.

In the terminal (Claude Code, Codex, Cursor), in your project folder:

npx skills add github/awesome-copilot --skill creating-oracle-to-postgres-master-migration-plan

Or download just the file:

curl -L https://raw.githubusercontent.com/github/awesome-copilot/main/skills/creating-oracle-to-postgres-master-migration-plan/SKILL.md -o SKILL.md
Technical content (original SKILL.md)

Original text by the author, straight from GitHub.

Creating an Oracle-to-PostgreSQL Master Migration Plan

Analyze a .NET solution, classify every project for Oracle→PostgreSQL migration eligibility, and write a structured plan that downstream agents and skills can parse.

Workflow

Progress:
- [ ] Step 1: Discover projects in the solution
- [ ] Step 2: Classify each project
- [ ] Step 3: Confirm with user
- [ ] Step 4: Write the plan file

Step 1: Discover projects

Find the Solution File (it has a .sln or .slnx extension) in the workspace root (ask the user if multiple exist). Parse it to extract all .csproj project references. For each project, note the name, path, and type (class library, web API, console, test, etc.).

Step 2: Classify each project

Scan every non-test project for Oracle indicators:

  • NuGet references: Oracle.ManagedDataAccess, Oracle.EntityFrameworkCore (check .csproj and packages.config)
  • Config entries: Oracle connection strings in appsettings.json, web.config, app.config
  • Code usage: OracleConnection, OracleCommand, OracleDataReader
  • DDL cross-references under .github/oracle-to-postgres-migration/DDL/Oracle/ (if present)

Assign one classification per project:

Classification Meaning
MIGRATE Has Oracle interactions requiring conversion
SKIP No Oracle indicators (UI-only, shared utility, etc.)
ALREADY_MIGRATED A -postgres or .Postgres duplicate exists and appears processed
TEST_PROJECT Test project; handled by the testing workflow

Step 3: Confirm with user

Present the classified list. Let the user adjust classifications or migration ordering before finalizing.

Step 4: Write the plan file

Save to: .github/oracle-to-postgres-migration/Reports/MasterMigrationPlan.md

Use this exact template — downstream consumers depend on the structure:

# Master Migration Plan

**Solution:** {solution file name}
**Solution Root:** {REPOSITORY_ROOT}
**Created:** {timestamp}
**Last Updated:** {timestamp}

## DDL Artifacts

**Location:** {path to DDL artifacts, e.g., `.github/oracle-to-postgres-migration/DDL/`}
**External tool used:** {Yes / No} — {If Yes, name the tool (e.g., `ora2pg`) and note that Phase 4 (Schema & DDL Migration) can be skipped; PostgreSQL DDL artifacts already exist.}

## Solution Summary

| Metric | Count |
|--------|-------|
| Total projects in solution | {n} |
| Projects requiring migration | {n} |
| Projects already migrated | {n} |
| Projects skipped (no Oracle usage) | {n} |
| Test projects (handled separately) | {n} |

## Project Inventory

| # | Project Name | Path | Classification | Notes |
|---|---|---|---|---|
| 1 | {name} | {relative path} | MIGRATE | {notes} |
| 2 | {name} | {relative path} | SKIP | No Oracle dependencies |

## Migration Order

1. **{ProjectName}** — {rationale, e.g., "Core data access library; other projects depend on it."}
2. **{ProjectName}** — {rationale}

Order projects so that shared/foundational libraries are migrated before their dependents.

FAQ

What does 'classification' mean?

It's a label the tool gives to each project to indicate if it uses Oracle (MIGRATE), doesn't use it (SKIP), has already been converted (ALREADY_MIGRATED), or is a test project (TEST_PROJECT).

Where is the plan saved?

The plan is saved in a file named 'MasterMigrationPlan.md' within the '.github/oracle-to-postgres-migration/Reports/' folder of your project.

Can I change the classifications?

Yes, the tool presents the list of projects and their classifications, allowing you to make adjustments before the final plan is generated.

Details

Original description by the author

Discovers all projects in a .NET solution, classifies each for Oracle-to-PostgreSQL migration eligibility, and produces a persistent master migration plan. Use when starting a multi-project Oracle-to-PostgreSQL migration, creating a migration inventory, or assessing which .NET projects contain Oracle dependencies.

repo: github/awesome-copilot

Popularity

GitHub stars
40k
Ranking position
#5091
License
MIT
Updated
10/15/2026

Is this skill useful?

0

Sign in to vote.

Comments

  • …

More skills from this repository

Similar skills