
Oracle to PostgreSQL Migration Plan
OfficialFreeStreamline your Oracle to PostgreSQL migration process.
Free · Opens the source repo
What Oracle to PostgreSQL Migration Plan does
The Oracle to PostgreSQL Migration Plan skill is designed specifically for developers working with .NET solutions that need to migrate their projects from Oracle databases to PostgreSQL. This skill automates the discovery and classification of projects within a .NET solution, enabling users to efficiently create a comprehensive migration plan. By parsing the solution file and analyzing each project for Oracle dependencies, this skill ensures that all relevant projects are accounted for in the migration process.
The workflow begins with the discovery of projects in the specified solution file, identifying each project’s type and path. Once the projects are listed, the skill classifies them based on their Oracle interactions, allowing developers to focus on those that require migration. This classification includes identifying projects that can be skipped, those that have already been migrated, and test projects that should be handled separately. The skill also provides an opportunity for users to confirm or adjust the classifications before finalizing the migration plan.
After confirming the classifications, the skill generates a structured master migration plan in Markdown format. This plan includes a summary of the solution, a detailed project inventory, and a recommended migration order, ensuring that foundational libraries are migrated before dependent projects. This structured approach not only aids in planning but also facilitates communication among team members and downstream tools that may rely on the migration data.
This skill is particularly useful for teams embarking on a multi-project migration initiative, as it helps maintain organization and clarity throughout the process. By automating the initial steps of migration planning, developers can save time and reduce the risk of overlooking critical dependencies.
When to use it
Use this skill when starting a multi-project migration from Oracle to PostgreSQL to ensure all dependencies are identified and documented.
When not to use it
This skill may not be suitable for single-project migrations or for projects that do not utilize Oracle databases.
What you can build with it
Starting a Migration Project
Use this skill to kick off a multi-project migration from Oracle to PostgreSQL, ensuring all dependencies are tracked.
Creating a Migration Inventory
Generate a detailed inventory of all projects in your .NET solution, classifying them based on their Oracle usage.
Assessing Project Dependencies
Quickly assess which projects in your solution require migration, helping to prioritize your efforts.
How to install Oracle to PostgreSQL Migration Plan
View source1. Install with the skills CLI
npx skills add github/awesome-copilot/creating-oracle-to-postgres-master-migration-plan --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by githubCreating 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.csprojandpackages.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/Master Migration Plan.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}
## 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.
Frequently asked questions about Oracle to PostgreSQL Migration Plan
Similar skills
ClickHouse Logs Queries
Efficiently manage Supabase logs with ClickHouse SQL.
EF Core D2 Database Diagram Generator
Visualize your EF Core models as D2 diagrams effortlessly.
Safe SQL Execution
Ensure secure SQL execution in Supabase applications.
Oracle to PostgreSQL Migration
Identify migration risks between Oracle and PostgreSQL.
SSMA Console
Streamline Oracle to SQL Server migrations with ease.
SQL Performance Optimization
Enhance SQL query efficiency across all databases.
