# Oracle EBS to Fusion Cloud Fit Gap Worksheet

> Source: https://netray.co/tools/oracle-fusion-ebs-migration-fit-gap-worksheet
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Capture each requirement, classify it as standard, configuration, extension or gap, and total the effort in days.

## Category

oracle

## Erp

Oracle Fusion Cloud SCM

## Audience

- Oracle Cloud consultant
- Business analyst
- EBS migration lead

## Tool

**Kind:** worksheet

**Mode:** editable

**Currency:** $

**Columns:**

#### Requirement

**Key:** req

**Type:** text

#### Module

**Key:** module

**Type:** select

**Options:**

- Inventory
- Manufacturing
- Procurement
- Order Management
- Planning
- Cost Management
- Quality
- Maintenance
- Other

#### Fit

**Key:** fit

**Type:** select

**Options:**

- Standard
- Configuration
- Extension
- Integration
- Process change
- Gap

#### Priority

**Key:** priority

**Type:** select

**Options:**

- Must
- Should
- Could

#### Effort (days)

**Key:** days

**Type:** number

#### Day rate

**Key:** rate

**Type:** number

**Format:** currency

#### Estimated cost

**Key:** cost

**Type:** number

**Expr:** days * rate

**Format:** currency

#### Owner

**Key:** owner

**Type:** text

**Rows:**

**Req:** Lot tracked items with expiry

**Module:** Inventory

**Fit:** Standard

**Priority:** Must

**Days:** 2

**Rate:** 900

**Owner:** Inventory lead

**Req:** Custom operation labels on shop floor

**Module:** Manufacturing

**Fit:** Extension

**Priority:** Should

**Days:** 8

**Rate:** 900

**Owner:** Plant IT

**Req:** Supplier scorecard from receipts

**Module:** Procurement

**Fit:** Integration

**Priority:** Should

**Days:** 12

**Rate:** 900

**Owner:** Procurement

**Req:** Order promising by plant

**Module:** Order Management

**Fit:** Configuration

**Priority:** Must

**Days:** 6

**Rate:** 900

**Owner:** OM lead

**Req:** Legacy 3-way cost roll report

**Module:** Cost Management

**Fit:** Gap

**Priority:** Could

**Days:** 15

**Rate:** 900

**Owner:** Finance

**Totals:**

#### Total effort (days)

**Key:** days

**Agg:** sum

**Format:** integer

#### Total estimated cost

**Key:** cost

**Agg:** sum

**Format:** currency

**Summary:**

#### Average effort per requirement (days)

**Key:** avg_days

**Expr:** sum_days / count

**Format:** decimal

**Primary:** true

#### Requirements listed

**Key:** lines

**Expr:** count

**Format:** integer

**Notes:** Replace sample rows with your own. Use Gap only where no standard, configuration or extension route exists, and record the workaround in the requirement text.

## Content

**Intro:** A fit gap analysis decides how much of your EBS behaviour survives in Oracle Fusion Cloud and what it costs to fill the rest. This worksheet captures each requirement with a fit class, priority and effort so you can total the work.

**Sections:**

#### How to use the worksheet

**Body:** List one requirement per row in business language, not screen names. Choose the module, classify the fit, set priority using Must, Should or Could, and estimate effort in days. Cost is computed from your day rate. Export to Excel for workshops, where business owners confirm or challenge each classification.

**Bullets:**

- Write requirements as outcomes
- Challenge every Gap with a process change option
- Review Must items first

#### Fit categories explained

**Body:** Standard means the product does it out of the box. Configuration means setup achieves it. Extension covers Application Composer, page personalization or extension code. Integration means an external system or REST and event based build is needed. Process change means the business adapts. Gap means no acceptable route exists today.

#### Common mistakes

**Body:** Teams copy every EBS customization as a requirement, rebuilding workarounds for problems Fusion already solves. Another trap is classing something as Standard without testing it in a sandbox. A third is estimating effort without including test and support, which usually exceeds build effort for extensions.

**Bullets:**

- Challenge legacy customizations before recording them
- Prove Standard fits in a demo environment
- Include test and support effort in estimates

**Cta:** If your fit gap list is long, we can help sort what an AI assistant over your Fusion and legacy data could replace, such as custom reports and lookups.

**Faq:**

#### How many gaps are normal?

**Answer:** It varies by industry and how customized the EBS system is. A high gap count usually signals unchallenged legacy customizations rather than true product limits. Review each gap with a process change option first.

#### What is the difference between extension and gap?

**Answer:** An extension is a supported way to add behaviour, for example with Application Composer or integration. A gap means no supported route exists and the business must accept a workaround or a different process.

#### Should I estimate in days or hours?

**Answer:** Days are usually enough at this stage. Detailed hour estimates belong to build planning once the fit classification and design are agreed with business owners.

#### Who signs off on fit decisions?

**Answer:** Business process owners accept the fit and any process change. Consultants advise, but sign off by the owner is what prevents rework when users see the design in testing.

## Search terms

oracle fusion fit gap analysis template, ebs to fusion fit gap, fit gap worksheet excel, oracle cloud fit gap, erp fit gap analysis template, oracle scm fit gap, requirements fit gap effort, oracle migration gap analysis

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json