Migration Backlog Not Exportable
The Migration backlog in the web portal turns your documentation into Epics, Features and User stories. aprity only enables the Excel and CSV exports when the backlog is complete, so that your team never receives a backlog with silent gaps. Until then, you can still browse the whole backlog.
The page shows one of two states, with the reasons listed under it.
"Qualification in progress"
Last step before export: complete the qualification
The backlog is built, but some user stories still need one more input: an actor, an acceptance criterion, an integration contract, or a validation by a business analyst.
Typical cases:
- No actor. aprity names an actor ("As a ...") only when your access settings point to exactly one active profile that can edit the object. When several profiles can, aprity does not choose one for you.
- Integration stories. A story about an external system stays blocked until its contract is complete: direction, trigger, data, authentication, error handling and retries.
- Low-confidence processes. Stories from a process that aprity identified with low confidence need a business analyst's validation.
What to do: review the blocked stories with your business analysts and complete what is missing.
"Partial backlog"
This backlog is still incomplete for a migration
Something is missing upstream, in the documentation the backlog is built from. The page lists the reasons:
| Reason shown | What to do |
|---|---|
| The Salesforce metadata fetch is incomplete on at least one documented object... | Open Coverage and fidelity > Coverage to see which components could not be read. Usually an access problem of the integration user. See Partial Documentation. |
| At least one object's detailed documentation was not produced... | The business rules of that object could not be generated. The next analysis usually fixes it; contact support if it persists. |
| The functional-process build failed... / ...finished in degraded mode... | The process map the backlog rests on is missing or incomplete. Run the next analysis; contact support if it persists. |
| No functional process map was produced for this scan. / The functional process map contains no process. | Same as above. On an org with very little automation, there may simply be no process to describe. |
| No business rule was analysed for this scan... | The analysis found no business rules to describe. Check that the org has automation, then see Empty or Missing Documentation. |
| The main backlog contains no user story — only traceability rows were produced. | The content is limited to a traceability inventory. |
| The scan completeness marker could not be read... | Regenerating the backlog is enough; a full new analysis is not needed. Contact support. |
When the export is available with a warning
If the metadata fetch is incomplete only on objects the backlog does not document, the backlog stays exportable and the page shows a notice instead: "The backlog remains usable and exportable."