A full inspection and emergency backup of the Mi Local Trades platform following loss of access to the original developer's source repositories.
The platform has been fully inspected and its critical assets secured. Every live database, customer record, payment, contract, backend function, the running application, and the Android release have been backed up to secure offline storage — more than 1 GB of business data and code, alongside a complete inventory of approximately 50 GB of media. No data was lost during the developer's departure. Two editable source-code repositories remain in the developer's private GitHub account and require transfer to the owner; this is the only outstanding item.
The investigation found the platform to be larger and healthier than initially feared. The previous developer had migrated the system to a newer backend — the mlt24-crm database — rather than deleting anything. The earlier data remains intact alongside the current system.
| System | Role | Status |
|---|---|---|
| mlt24-crm | Live production database — 997 leads, 145 payments, 26 users | Secured |
| milocaltrades | Previous version — superseded but intact | Secured |
| getleads | Staging copy of the live system | Secured |
| Website | milocaltrades.com — marketing site and customer portals | Recoverable |
| Lead & Job app | Salesman application — web and Android from one codebase | Build saved |
| Background services | Link redirector, payment proxy, media worker | Config saved |
| Asset | Detail | Result |
|---|---|---|
| Live database | 51 tables — leads, payments, contracts, invoices, subscribers, support tickets, 1,566 short links | Complete |
| Previous & staging databases | 32 + 51 tables — full history preserved | Complete |
| Backend functions | 45 total — payments, SMS, push, invoicing, signatures, in-app purchases | Complete |
| Documents & images | 639 MB — quote PDFs, signed contracts, logos, sample images | Complete |
| Media inventory | Full catalogue of ~50 GB of video and media, ready for server-to-server transfer | Catalogued |
| Running application | The complete live Lead & Job app (web build) | Complete |
| Android release | Original AAB, signed APK, archived APK — build 107, v2.4.2 | Complete |
| Payment proxy source | Full source code recovered from GitHub | Complete |
| Service configuration | All 3 background services — build commands, settings, environment variable names, domains | Complete |
| Website | Full file structure, configuration, build settings, environment variable names | Documented |
These cannot be recovered without the developer, as they reside in his private GitHub account and were never accessible to anyone else:
Recommended action: while the developer is cooperating, request that these repositories be transferred to the owner's GitHub account. This is the single most valuable remaining step.
Recovery was carried out as a focused, full-time effort across all platforms. Approximate hours by workstream:
| Workstream | Scope | Hours |
|---|---|---|
| Platform investigation | Inspected Vercel, Render, Supabase, Google Play; mapped the full architecture | 4.0 |
| Live-version analysis | Identified the migration to mlt24-crm; ruled out duplicate systems | 2.0 |
| Database backups | Pulled all 134 tables of live and historical data across 3 databases | 3.0 |
| Backend functions | Downloaded all 45 functions across two projects | 1.5 |
| Storage & media | Retrieved 639 MB of documents; catalogued ~50 GB of media | 2.5 |
| Application & Android | Mirrored the live app build; secured the Android release | 2.0 |
| Website, services & GitHub | Captured website source and config, service configs, recovered available repository | 3.0 |
| Reporting & handoff | Documentation, this report, and the handoff package | 2.0 |
| Total | ~20.0 |
The recovery package is approximately 1 GB of databases, code, functions, documents, and application builds. The large media library is catalogued rather than copied, to keep the package portable. Recommended methods of secure transfer:
The package is uploaded to a private, password-protected cloud folder. The owner receives the link and password separately. Best suited to a package of this size — no software required.
Rather than handing over raw files, the data is restored into new accounts the owner controls — a fresh database, repositories under the owner's GitHub, and redeployed services. The result is a running system owned outright, not a folder of files.
A single compressed archive for offline safekeeping, transferred by encrypted file transfer or physical drive.
databases/ — all 3 databases as structured data · functions/ — all 45 backend functions · app/ — live app build and Android release · services/ — service configs and recovered proxy source · website/ — structure, configuration, source · media-inventory/ — catalogue of the media library · README — guide to each folder.
Request that the developer move the application and website repositories to the owner's GitHub account while cooperation is available.
Reset the third-party keys — payments, SMS, email — so that only the owner holds them. The backup identifies exactly which keys are in use.
Move the live database, functions, website, and application into accounts and repositories the owner controls, removing any remaining dependency on the previous developer.