Migration Backlog

The Migration backlog turns your documentation into a backlog: Epic → Feature → User story, with acceptance criteria written as Given / When / Then / Unless. It describes what the org does today, in a form that a team rebuilding or migrating it can plan, estimate and test against.

It is generated automatically after each scan, without AI at build time: it reuses the business rules, functional processes and integrations already documented. It is included on every plan.

Open it from Migration backlog in the Migration group of the portal rail.

When to use it

• Migrating to another CRM or rebuilding the org -- hand the backlog to the team that builds the target.
• Planning acceptance testing -- each user story carries acceptance criteria.
• Estimating -- portability tags show which stories carry over as-is and which need rework.
• Onboarding -- the epics give a functional map of what the org does.

To write new stories for a change you want to make, use the Story Agent instead.

Is the backlog ready?

The header states whether the backlog can be handed over:

Status	Meaning
Up to date	Every user story in the main backlog is complete. Excel and CSV exports are available.
Qualification in progress	The structure is there, but some user stories await one more input -- an actor, an acceptance criterion, an integration contract or a BA validation. The backlog is browsable; exports activate once it is complete.
Partial backlog	Something upstream is incomplete (for example the functional process map, the business rules of an object, or part of the metadata fetch). The content remains browsable for traceability; exports activate once a complete backlog has been generated.

The page lists the exact reasons. Some can be fixed by regenerating the backlog; others need a new scan. See also Coverage and fidelity for what the scan covered.

What you see

• Backlog summary -- the number of Epics, Features and User stories.
• Backlog preview -- the tree of epics, features and user stories, with a search box and a Portability filter. Large backlogs show the first epics; download the file for the full backlog.
• End-to-end journeys -- business flows that span several objects. They reference the epics; they do not duplicate their stories.
• Traceability & cross-cutting -- business rules not yet expressed as a capability, plus cross-cutting capabilities. They are listed so nothing is lost, without being presented as user stories.
• Inventory -- source artefacts with no behaviour to narrate, listed for completeness.

Where epics come from

• Functional processes become epics, with features grouped by phase. See Functional Processes.
• External systems become integration epics ("Integration with ..."). An integration story stays not ready until its contract is complete: direction, mechanism, trigger, data, authentication, error handling, operation, retries and idempotency.

Inside a user story

• As a / I want / so that -- "As a" is filled only when your org's access data designates a single human profile for the capability; aprity leaves it empty rather than guess. "So that" is filled only when a source states the objective.

• Acceptance criteria -- Given / When / Then / Unless, derived from the business rules. Salesforce API names are replaced by the labels your org uses where they are known.

• Actor and Security profile, when established.

• Portability:

  Tag	Meaning
  Portable as-is	Business behaviour that carries over to any platform.
  Formula to rewrite	Relies on a Salesforce formula.
  Automation to rebuild	Relies on Salesforce automation (flow, workflow...).
  OmniStudio to reimplement	Relies on OmniStudio.
  Code to redevelop	Relies on Apex code.

• Impacted components, Risks, and a Documentation confidence indicator.

• Stories from processes with low confidence are flagged for BA review.

You can give feedback on any user story (Give feedback on this user story). See Feedback and Human Corrections.

Downloading the backlog

When the backlog is Up to date, two downloads are available:

• Download Excel (.xlsx) -- three sheets: Backlog (every epic, feature and story in one table, with acceptance criteria, tags and traceability to the source components), Insights (counts and portability distribution) and Diagrams (one diagram per epic).
• Download CSV -- the backlog table only, for import into a tracker or further processing.

The files contain your business logic: treat them as confidential.

The backlog is not pushed to a tracker automatically. Import the CSV with your tracker's importer.

Good to know

• The backlog reflects the version selected in the portal. Run a new scan to reflect the latest state of the org.
• It is written in the language of the documentation.
• Rules are grouped into user stories by section and theme, with a limit on the number of rules per story. If your project needs a different granularity, contact contact@aprity.ai.
• Story text is derived from the source metadata and remains traceable to it; it is not a substitute for the metadata itself.