Overview
This guide helps you migrate existing AI workflows from other frameworks to Nadoo Flow Core. We cover the most common patterns and provide code examples for smooth transitions.From LangChain
Basic Chain Migration
- LangChain
- Nadoo Flow Core
Sequential Chain
- LangChain
- Nadoo Flow Core
Memory/Chat History
- LangChain
- Nadoo Flow Core
Retrieval QA
- LangChain
- Nadoo Flow Core
From CrewAI
Agent Migration
- CrewAI
- Nadoo Flow Core
Multi-Agent Workflow
- CrewAI
- Nadoo Flow Core
From AutoGen
Conversational Agents
- AutoGen
- Nadoo Flow Core
Migration Checklist
1
Assess Current Implementation
- List all chains/agents/workflows
- Identify external dependencies
- Document data flows
- Note any custom components
2
Plan Migration
- Prioritize workflows by complexity
- Identify reusable patterns
- Plan for testing strategy
- Schedule migration phases
3
Migrate Core Workflows
- Start with simplest workflows
- Convert one workflow at a time
- Test thoroughly
- Update integrations
4
Update Dependencies
- Install Nadoo Flow Core
- Update import statements
- Configure environment
- Update deployment configs
5
Test & Validate
- Unit test each workflow
- Integration testing
- Performance testing
- User acceptance testing
6
Deploy
- Deploy to staging
- Monitor for issues
- Gradual rollout to production
- Keep old system as fallback
Common Patterns
Pattern 1: Simple LLM Call
Pattern 2: Chain of Operations
Pattern 3: Parallel Execution
Pattern 4: Conditional Logic
Troubleshooting
Async/Await Issues
Async/Await Issues
Problem: Your old code was synchronousSolution:
- Add
asyncto function definitions - Use
awaitfor all node executions - Update calling code to handle async
Data Format Differences
Data Format Differences
Problem: Input/output formats don’t matchSolution:
- Use FunctionNode to transform data
- Create adapter nodes
Missing Features
Missing Features
Problem: Framework-specific features not availableSolution:
- Implement custom nodes
- Use parallel workflows
- Check Flow Core examples
- Request feature via GitHub
Performance Issues
Performance Issues
Problem: Migration is slower than expectedSolution:
- Enable async throughout
- Use ParallelNode for independent tasks
- Implement caching
- Profile and optimize bottlenecks
Best Practices
1. Incremental Migration
Don’t migrate everything at once:2. Maintain Backward Compatibility
Create compatibility layers:3. Test Continuously
4. Document Changes
Keep a migration log:Getting Help
Discord Community
Ask migration questions
GitHub Issues
Report migration issues
Examples
Browse migration examples
Comparison
Framework comparison guide