Which migration is most relevant to your current work?
- SDK
- API (REST/GraphQL/gRPC)
- Both SDK and API
- Not sure yet
Which SDK language(s) are in scope for this migration?
- JavaScript/TypeScript
- Python
- Java/Kotlin
- Swift/Objective-C
- C/.NET
- Go
- Ruby
- PHP
- C/C++
- Rust
Which API style(s) are in scope?
- REST
- GraphQL
- gRPC
- WebSocket
- Webhooks
Briefly describe which components will use the SDK and which will call the API.
Max 600 chars
Which platform(s) are involved in this migration?
- Web frontend
- iOS
- Android
- Backend services
- Data pipelines
- Desktop apps
- IoT/Embedded
- CLI/Automation
Which best describes your migration status today?
- Not started
- Planning
- In progress
- Completed in test/staging
- Completed in production
- Not planning to migrate
If in progress, about what percent complete? (0-100)
Accepts a numeric value
Whole numbers only
If planning or not started, when do you expect to begin?
- Within 1 month
- 1-3 months
- 3-6 months
- 6-12 months
- More than 12 months
- Not sure
If completed, what outcomes have you observed?
- Reliability improved
- Performance improved
- Access to new features
- Security/compliance improved
- Maintainability improved
- Cost reduction
- No noticeable change
If not planning to migrate, what is the primary reason?
- Dependencies on legacy components
- Lack of time/resources
- Low perceived benefit
- Risk of regressions
- Customer commitments block changes
- Waiting for missing features
- Budget constraints
- Limited internal expertise
Rate how much each factor is a blocker for your migration.
| Rows | Not a blocker | Minor | Moderate | Significant | Major |
|---|
| Documentation clarity | • | • | • | • | • |
| Migration guide completeness | • | • | • | • | • |
| Backward compatibility/shims | • | • | • | • | • |
| Sample code coverage | • | • | • | • | • |
| SDK/API stability/versioning | • | • | • | • | • |
| Performance benchmarks | • | • | • | • | • |
| Security/compliance approvals | • | • | • | • | • |
| Support responsiveness | • | • | • | • | • |
Rank your top blockers to address first (most important at top).
Drag to order (top = most important)
- Internal dependencies
- Missing/unclear documentation
- Breaking changes
- Insufficient test coverage
- Security review process
- Stakeholder buy-in
Estimate total engineer-days needed to complete the migration.
Accepts a numeric value
Whole numbers only
Allocate 100 points to show where effort will go.
Total must equal 100
- Planning/design
- Code changes
- Writing/maintaining tests
- Data migration
- Integration/CI/CD updates
- Documentation and training
- Security/compliance review
- Stakeholder coordination
Min per option: 0Whole numbers only
What would help you move faster in the next 30 days?
- Dedicated migration guide
- Code examples for my stack
- Starter templates
- Compatibility layer/tools
- Linting/static analysis rules
- Office hours with engineers
- Faster responses in forum/Slack
- Feature roadmap clarity
- Migration checklist
Where do you primarily look for migration information?
- Product docs site
- GitHub repo/README
- Community forum
- Stack Overflow
- Blog posts/tutorials
- Company Slack/Discord
- Colleagues/internal wiki
What is your primary role?
- Backend engineer
- Frontend engineer
- Mobile engineer
- Full-stack engineer
- DevOps/SRE
- Data/ML engineer
- Architect/Tech lead
- Product manager
- Engineering manager
- Other
How many years of professional experience do you have?
Company size (employees)
- 1-10
- 11-50
- 51-200
- 201-1000
- 1001-5000
- 5001-10000
- 10000+
Primary region/time zone
- Americas
- EMEA
- APAC
- Other/Multiple
Industry
- Technology/SaaS
- Finance/Fintech
- E-commerce
- Healthcare
- Media/Gaming
- Education
- Government/Nonprofit
- Other
Attention check: please select "I am paying attention".
- I am paying attention
- I am not paying attention
- Prefer not to say
Welcome! This quick survey takes a few minutes and helps us understand your migration needs. Please answer based on your current project.
Any other comments or context we should know to support your migration?
Max 600 chars
AI Interview: 2 Follow-up Questions on Migration Readiness
AI InterviewLength: 2Personality: Expert InterviewerMode: Fast Thank you for your time—you're all set.