Interface Migration Guide: PilotFish Solutions
Migrating from a legacy integration platform like BizTalk, Cloverleaf or Mirth can be complex, but it doesn’t have to be. PilotFish provides the tools, methodology and best practices to streamline Interface migration and dramatically reduce time, cost and risk.
This guide walks you through the complete migration process using PilotFish’s visual tools and best-in-class 7-stage Assembly Line architecture.
1. Assess and Prioritize Your Interfaces
- Inventory and Categorize: Start by listing your existing Interfaces and sorting them by complexity, frequency of use and business impact.
- Prioritize for Success: Focus on low-complexity or high-value interfaces first to build confidence and demonstrate early wins.
- Establish KPIs: Define what success looks like from the start—e.g., deployment speed, message volume or error rates—to track progress throughout the migration project.
2. Leverage PilotFish’s 7-Stage Assembly Line Architecture
PilotFish’s self-documenting Assembly Line breaks every integration into clear, modular Stages:
Stage 1. Listener: Receives incoming data
Stage 2. Source Transformation: Converts data to your standard internal format
Stage 3. Route: Directs messages based on defined rules
Stage 4. Target Transformation: Converts to the target system’s format
Stage 5. Transport: Sends the data
Stage 6. Error Handling: Catches and manages exceptions
Stage 7. Post Processors: Handles final actions like archiving or logging
Use this architecture to deconstruct and rebuild each legacy interface, stage by stage.
3. Extract and Rebuild Schemas & Data Mappings
- Export Existing Logic: Extract XML schemas, flat file definitions and transformation logic (e.g., XSLT from BizTalk).
- Use PilotFish’s Data Mapper:
- Supports all major Formats: XML, JSON, HL7, X12, CSV, databases and proprietary formats
- Drag & drop mapping with 100+ built-in functions (string, math, logic, date/time, etc.)
- Inline testing to verify outputs as you go
- Modular Mapping: Create reusable transformations and templates for similar data flows to reduce effort and speed future migrations.
4. Configure Listeners and Transports
- Configure Your Connectors: PilotFish provides built-in support for:
- SFTP, FTP, HTTP, TCP, JMS, SMTP, Web Services (SOAP/REST) and more
- Listeners receive incoming messages; Transports deliver them.
- Use consistent naming conventions for clarity and future manageability.
5. Implement Routing and Business Logic
- Define routing rules using:
- XPath expressions
- XSLT logic
- Regex
- Scripted processors
- Apply business rules modularly using built-in or custom Processors (e.g., lookup tables, enrichment, validation).
- Keep logic flexible and reusable for future interfaces.
6. Use Inline Testing Early and Often
- Stage-by-stage testing lets you independently validate each part of the Assembly Line.
- Test with real or sample data and view full traceable message flows.
- Resolve errors at the source before full deployment to save debugging time downstream.
7. Adopt Iterative, Side-by-Side Deployment
- Migrate incrementally: Run PilotFish in parallel with your legacy system.
- Deploy interfaces one at a time, test in production conditions and gradually switch over.
- This minimizes risk and allows for rapid rollback if needed.
8. Document as You Build
- While PilotFish interfaces are self-documenting, maintain a migration log or project workbook:
- Capture transformation rules, mapping logic, test data, decisions and known issues
- This promotes transparency, simplifies maintenance and enables easier handoff to other team members.
9. Establish Naming and Versioning Standards
- Define and enforce naming conventions for:
- Interfaces
- Routes
- Mapping files
- Use version control to track interface changes, enable rollback and support multi-environment deployments (Dev, Test, Prod).
10. Deploy and Monitor with eiDashboard
- Use the PilotFish eiPlatform runtime to deploy completed interfaces.
- Monitor all message activity in real-time via the PilotFish eiDashboard:
- Search, track and troubleshoot individual messages
- Configure alerts for failures or performance anomalies
- Built-in logging and auditing help you maintain operational visibility and compliance.
11. Optimize and Scale Your Migration
- After the first wave of migration:
- Identify reusable logic
- Automate recurring processes
- Retire duplicated or obsolete interfaces
- Scale your migration efforts by applying lessons learned, reusing components and expanding PilotFish across departments or customer integrations.
12. Engage PilotFish Support & Services
- PilotFish offers:
- Migration planning and review sessions
- Custom onboarding and training
- Architecture validation
- Best practice implementation workshops
- PilotFish support and & services experts help reduce learning curves and accelerate your time to production.
Learn more about how PilotFish simplifies interface migration with no coding required. Below are answers to common questions about side-by-side deployment, testing and accelerating migration projects.
Interface Migration Frequently Asked Questions
What is the best approach for migrating from BizTalk?
The best approach is a phased migration using side-by-side deployment. Start with low-complexity interfaces, use PilotFish’s visual Assembly Line architecture and test extensively at each stage to ensure accuracy and minimize disruption.
How does PilotFish support replacing legacy interfaces?
PilotFish’s visual integration tools make it easy to rebuild and replace legacy interfaces. With reusable components, inline testing and step-by-step control through its Assembly Line architecture. PilotFish helps your team modernize connections between systems quickly and reliably.
How long does a typical interface migration take with PilotFish?
Timelines vary based on complexity, but most users find they can rebuild and deploy interfaces significantly faster than with traditional platforms—often in days or weeks, not months.
What tools does PilotFish offer for testing and validation?
PilotFish includes inline testing within its Data Mapper, full message tracing and a real-time eiDashboard for validating transformations and tracking message flow through every stage.
Does PilotFish offer migration services and support?
Yes. PilotFish offers architecture reviews, custom onboarding, planning workshops and implementation support to help your team accelerate time to production and ensure best practices.
Check out our FAQ pages for more.