MFT implementation
Managed file transfer, implemented without disrupting your partners
Moving file transfers onto a managed platform means inventorying what runs today, designing secure connections, testing with every partner and cutting over without missing a file. ECOM's specialists plan and carry out the implementation, then support the platform or hand it to your team.
At a glance
- Inventory and assessment
- Design
- Partner connections
- Testing and cutover
- Handover and support
What is an MFT implementation?
A managed file transfer implementation sets up a governed platform for exchanging files with partners and between internal systems. It covers the inventory of existing transfers, protocol and security design, partner connections, monitoring and alerting, testing, cutover and the operating procedures that keep transfers running.
Why teams choose it
Benefits
No missed files at cutover
Transfers move in planned waves with parallel testing and rollback plans agreed with each partner.
Secure by design
Protocols, encryption, keys and access are designed up front instead of added transfer by transfer.
Ready to operate
Monitoring, alerts and procedures are in place from go-live, whether your team or ECOM runs the platform.
Scope
What's included
-
Inventory and assessment
Identify existing transfers, partners, schedules, owners and the scripts or servers they run on.
-
Design
Choose protocols, security, folder and routing rules for each partner and internal flow.
-
Partner connections
Configure AS1, AS2, AS3, AS4, SFTP, FTP, FTPS, HTTP/HTTPS and SMTP connections, as server or client.
-
Testing and cutover
Test each connection with the partner and cut over in waves with rollback options.
-
Handover and support
Documentation and training for your team, or ongoing operations through ECOM's delivery models.
Fit
When it fits
Retiring scripts and FTP servers
Scattered scripts and unsupported FTP servers are replaced with one governed platform.
Audit findings
Unencrypted or unmonitored transfers flagged by an audit are moved to secure, logged connections.
Platform upgrades and migrations
Transfers move from an aging MFT product to a current platform, including IBM Sterling File Gateway.
Implementation
How implementing MFT Implementation Services works
Every project follows the same five stages. What changes is who does each task, which depends on the delivery model you choose.
-
Discover and scope
- ECOM
- Reviews your trading partners' requirements, documents, systems and volumes, and confirms the scope in writing.
- Your team
- Share partner guides or vendor manuals, sample documents, your ERP and version, and your deadlines.
-
Design and build
- ECOM
- Designs the flows and builds the maps, rules and connections, or supports your team building them on the platform.
- Your team
- Confirm business rules and field meanings, and provide test data and access to the right people.
-
Test and certify
- ECOM
- Tests each document internally, then completes the partner's testing or certification steps.
- Your team
- Check test results in your own systems and approve them before go-live.
-
Transition and go-live
- ECOM
- Plans the cutover, including a move from a current provider or platform, and watches the first live transactions.
- Your team
- Approve the go-live date and coordinate your internal teams and partner dates.
-
Support and improve
- ECOM
- Monitors and supports the integration as your delivery model and service agreement define, and handles partner changes in scope.
- Your team
- Tell ECOM about business changes, new partners and priorities.
What affects timing and price
ECOM sends a scoped proposal after reviewing your requirements. These factors make the most difference:
- How many trading partners and document types are in scope
- Each partner's testing and certification process and schedule
- Your ERP or application, and whether a standard connector fits or custom integration is needed
- Custom business rules, data quality and the work needed to map them
- Connection methods (AS2, SFTP, VAN, API) and security requirements
- Delivery model and support coverage, for example 24×7
- Transaction volumes and any migration from an existing platform
Frequently asked questions
How long does an MFT implementation take?
It depends on the number of transfers and partners, the protocols involved and each partner's testing schedule. ECOM sends a scoped plan after the inventory.
Can ECOM implement IBM Sterling File Gateway?
Yes. ECOM implements, upgrades and supports IBM Sterling File Gateway and Connect:Direct, as well as its own platform.
Who runs the platform after go-live?
Your team, ECOM or both. EDI Team as a Service and fully managed options are available, with responsibilities set in your agreement.
Plan your MFT implementation
Tell us how many transfers and partners you have and where they run today. ECOM outlines the plan and timeline factors.