Migrating legacy data to your Django project
summary
Migrates WordPress data into Django models using Django’s multiple-database support and inspectdb to generate models then custom management commands that run against a legacy DB router; handles media by saving images from original URLs, uses a local cache and bulk_create with batching plus pagination to avoid RAM blowups; notes Django skips validation on bulk saves, warns to clean or transform dirty content (examples include exported Access XML and 150,000 historic files), and reports runs taking from an hour up to eight hours.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:31Legacy Data What Is It
- 5:18Django Multiple Database Support
- 7:27Django Extensions
- 10:20Importing the Post
- 15:30Bulk Create
- 16:04Pagination
- 24:09Takeaways
related talks
21mMigrating to Success: Unleashing the Power of Django Migrations
28mIntegrating Django and WordPress can be simple.
43mDigging Into Django's Migrations
25mFrom Legacy to Admin
30m"Using Multiple Databases in Django Applications"
31mThis Old Pony: Working With Legacy Django Apps
23mBeyond the Basics of Migrations
21mBuilding maintainable Django projects: the difficult teenage years