Hello! I need help transferring my database between my original project (Project 1) to my new revamped/rebuilt project (Project 2).
Project 1 (Current):
-Technology Stack: PHP-based platform using MariaDB as the database.
-Purpose: Manages audio presets where users can upload, share, and download .xml files.
-File Storage: Files are stored in /var/www/html/files/upload/files/ with masked or extended filenames (e.g., 1666125643-ae7481973e6c9f63ea91e7cd1b77d8821b8e072d-Disturbed-Down-With-The-Sickness.xml).
-Database:
–User data is stored in a table called tbl_users.
–Preset file metadata is stored in tbl_files.
–Action logs (user activity such as uploads, downloads, and logins) are stored in tbl_actions_log.
–Category (plugin) information is stored in tbl_categories.
Project 2 (New):
-Technology Stack: Django-based platform using MySQL.
-Purpose: The next version of the platform, built to enhance user experience and scalability.
-File Storage: Files will be stored in /var/www/PresetJunkie/media/.
-Database:
–User data is stored in the Django default auth_user table.
–Preset file metadata is stored in a custom table called presetjunkie_preset.
–User actions (e.g., uploads, downloads) are stored in presetjunkie_actionlog.
Scope of Work:
I’m seeking a database professional to help migrate data and files from Project 1 to Project 2. The migration involves renaming columns, mapping data correctly between tables, and ensuring that all relationships (e.g., user uploads, action logs) are preserved. Below are the key components of the migration:
Key Considerations for Migration:
1. User Data Migration:
-Source: tbl_users (Project 1)
-Target: auth_user (Project 2)
-Adjustments:
–Renaming Columns: For example, user in Project 1 needs to be mapped to username in Project 2, and timestamp to date_joined.
–Password Hashing: Project 1 uses bcrypt for password hashing, while Project 2 uses Django’s PBKDF2 by default. We may need to ensure compatibility or transfer passwords without forcing users to reset them.
2. Preset File Metadata Migration:
-Source: tbl_files (Project 1)
-Target: presetjunkie_preset (Project 2)
-Adjustments:
–Column Mapping: For example, filename in Project 1 will map to title in Project 2, and url to file (which points to the physical file location).
–Category/Plugin Association: The category or plugin from Project 1’s tbl_categories will need to be linked properly to presets in Project 2.
–Download Counts: Ensure total downloads per file are preserved.
3. Action Logs Migration:
-Source: tbl_actions_log (Project 1)
-Target: presetjunkie_actionlog (Project 2)
-Adjustments:
–Mapping Action Types: Actions like uploads, downloads, and logins will need to be mapped correctly from Project 1 to Project 2.
–User References: Ensure user IDs in Project 1 are correctly mapped to user IDs in Project 2.
4. File Transfer and Path Adjustments:
-Source: Files stored in /var/www/html/files/upload/files/ (Project 1)
-Target: Files to be moved to /var/www/PresetJunkie/media/ (Project 2)
-Adjustments:
–Masked Filenames: Project 1 uses masked filenames for security (e.g., 1666125643-ae7481973e6c9f63ea91e7cd1b77d8821b8e072d-Disturbed-Down-With-The-Sickness.xml). These files will need to be transferred while maintaining metadata integrity.
–Updating File Paths: After transferring the physical files, the database references (file paths) in Project 2 must be updated to reflect the new location.
5. Data Integrity and Testing:
-Ensure that all foreign key relationships (e.g., linking users to presets, and presets to action logs) are maintained during the migration.
-Perform validation post-migration to ensure that:
–Users can log in without issues.
–Preset files are accessible and correctly linked to their respective metadata.
–Action logs are intact and reference the correct users and files.
Expected Deliverables:
-Fully migrated user data from Project 1 to Project 2, with correct mapping and column renaming.
-Complete transfer of preset metadata and file paths, ensuring files are accessible in Project 2.
-Action logs migrated and properly linked to the appropriate users and files.
-Physical file transfer from Project 1 to Project 2 (which I will take care of), with updated file paths in the database.
Ideal Candidate:
-Extensive experience with MySQL, MariaDB, and database migrations.
-Familiarity with Django’s auth_user and custom data models.
-Experience in handling file transfers and database table mapping.
-Ability to maintain data integrity and perform tests to verify a successful migration.
