
Migrating an AI driven system
- or -
Post a project like this- Posted:
- Proposals: 45
- Remote
- #4497708
- OPPORTUNITY
- Expired











Description
The platform includes doctor/surgeon matching, treatment mapping, clinical trial matching, support services, and 350+ city coverage.
I have a full technical brief, migration plan, and checklist ready.
Can you confirm you’re comfortable rebuilding the backend (Node/Python/PHP), integrating AI APIs, and deploying to a standard hosting environment?”
Lloyd L.
0% (0)New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-

Hi Lloyd,
A few technical questions before confirming the ideal stack approach:
1. What parts of the current Base44 platform are exportable?
database
-workflows
-API schemas
-frontend code/assets
-user data
2. Do you already have a preferred backend stack for the rebuild?
(Node, Python, Laravel/PHP, hybrid, etc.)
3. What Swiss hosting environment are you using?
(Dedicated server, VPS, shared hosting, cloud provider, Docker support, etc.)
4. Are the AI workflows already defined in the current platform, or would part of the task involve redesigning/improving them during migration?
5. Will the frontend/UI also be migrated/rebuilt, or is the focus primarily backend infrastructure and integrations?
Looking forward to your answers.
Best Regards.
-

Hi Lloyd,
Before planning the migration I’d like to understand whether the current Base44 implementation already exposes reusable APIs/data structures that can be ported cleanly, or if part of the work involves reverse-engineering business logic and rebuilding core workflows from scratch? Also, regarding the AI-driven matching components, are they primarily prompt/API orchestration layers on top of structured medical datasets, or do they include custom ranking, recommendation, and workflow logic that must be preserved exactly during deployment to your Swiss hosting environment?
Thanks
Naresh -

Can you share the current stack details and hosting environment you’ll be using in Switzerland?
-

* Is the current Base44 system already live in production with active users/data, or is this still pre-launch?
* Do you currently have access to the underlying database/schema/API structure, or would part of the work involve reverse-engineering existing platform logic?
* Which AI services/models are currently being used for matching, recommendations, or medical workflows?
* Are there any compliance/privacy requirements around medical data handling (GDPR, HIPAA-style practices, Swiss hosting/data residency requirements, etc.)?
* Does the migration involve rebuilding only the backend infrastructure, or also frontend/admin/dashboard functionality?
* How are doctor/surgeon matching and clinical trial matching currently handled — rules-based logic, AI embeddings/vector search, manual curation, or a hybrid system?
* Roughly how much data/content already exists in the platform (providers, cities, treatment mappings, users, articles, etc.)?
* Is the Swiss hosting environment a VPS/cloud server with full deployment control, or shared hosting with restrictions?
* Do you expect the rebuilt platform to support future scaling/features beyond the current Base44 implementation?
* Are there third-party integrations involved besides AI APIs (maps, CRM, auth providers, payments, analytics, email systems, etc.)?
* Do you already have a preferred backend stack for the rebuild (Node.js, Python, PHP), or are you open to recommendations based on scalability and AI workflow requirements?
* What would define a successful migration for you operationally — feature parity only, improved performance/stability, cleaner architecture, or future extensibility as well?