Start after the architecture decision
This guide assumes a web rebuild has been justified. If that decision is still open, start with the migration planning guide. A new framework is not a substitute for understanding the working database.
Map objects by responsibility
- Tables and relationships become a reviewed relational schema and Django models.
- Queries become database queries or reporting logic, preserving filters, joins and aggregate behaviour.
- Forms become validated browser workflows, not a screenshot-by-screenshot copy.
- Reports become agreed views or exports whose totals are checked against known examples.
- VBA and macros become explicit application services or scheduled tasks, with tests around each business rule.
Keep a cross-reference from the old object name to the new implementation and test. Mark retired objects and the person who approved retirement.
Define keys, validation and transactions
For an illustrative order-and-lines model, keep each line attached to its order, preserve legacy identifiers and decide how money, tax and rounding are represented. Test zero quantities, deleted products, missing customers and duplicate imports. Use database constraints for invariants and transaction boundaries for operations that must succeed together.
Make import batches repeatable: stage data, validate it, log rejected records and prevent a rerun from duplicating orders. Retain source snapshots and reconciliation outputs for the same batch.
Enforce permissions on the server
Django provides users, groups and model permissions. Record-level access still needs deliberate implementation and tests. A staff member who cannot see an export button must also be unable to call its endpoint.
Specify roles with allowed and denied actions, then test both. Review Django’s permission system. Never assume authentication alone enforces the business’s approval rules.
Use the admin for the right audience
The Django admin is intended for internal management. It can help authorized staff maintain reference records, but a customer portal or multi-step approval process may need purpose-built screens.
Ask users to complete a task without developer assistance. Check labels, search, keyboard navigation, validation errors and empty states, as well as the happy path.
Test integration and release failures
Specify timeouts, retries and duplicate protection for external requests. Test a background job twice, an unavailable provider, an interrupted import and a user editing a stale record. Compare reports against approved Access outputs and explain intentional differences.
Rehearse the write freeze, final import, reconciliation and rollback with a copy of representative data. Do not enable simultaneous writers without a tested synchronization design. Set recovery and support ownership before launch.
Review application examples without assuming migration evidence
ImageWing is Netvibes’ own web utility work, not an Access migration client case. It provides application context, not proof of migrated business data. Discuss the records, roles and integrations your own Django application would require.




Comments
Leave a comment
Comments are reviewed before publishing.