Migration path

Global Relay to SFTP migration

Global Relay → SFTP

Need to export email archive data from Global Relay to SFTP? We’ll manage the extraction, transfer, exceptions and agreed reporting from one migration plan.

Fully managed delivery
No customer-side install
Architecture deployed for the job
Agreed chain-of-custody reporting

Get a migration quote Talk to a migration engineer

What a Global Relay to SFTP migration involves

Source considerations — Global Relay

Leaving Global Relay starts with the approved archive scope, available access and supported export route. We confirm those details before scheduling batches or promising a delivery date.

Destination considerations — SFTP

Before delivering to SFTP, we agree the endpoint, authentication, directory and file conventions, retention window and evidence required for acceptance.

How we run the migration

Confirm the scope
We agree the data in scope, source access, destination requirements, volume, timing and evidence needed at handover.
Design and deploy the route
We select the supported migration method and deploy the eMXport architecture needed for the job.
Run and manage the work
We operate the migration jobs, monitor progress and investigate exceptions. Your team gets clear updates without running the platform.
Reconcile and report
We close the engagement against the agreed scope and provide the chain-of-custody and outcome reporting defined during discovery.

What we need to price the migration

Start with what you know. We can refine the rest during discovery.

Source and destination platforms
Approximate data volume in terabytes
Number of users, custodians or archives, where known
Required timescale and any fixed cut-off date
Retention, hold, legal or compliance constraints
Reporting and sign-off requirements

Get a migration quote

Questions we hear a lot

Do we need to install eMXport?: No. We deploy and operate the eMXport architecture for the engagement. Your team provides the agreed access and decisions, not another platform to maintain.
Can you preserve every folder, label, field and retention setting?: That depends on what the source can export and the destination can accept. We map the supported data and metadata during discovery, then document the agreed scope.
How long will the migration take?: Volume is only one factor. Source performance, destination limits, data shape, access, exceptions and migration windows all matter. We estimate timing after discovery.
Which format will the exported archive use?: The format depends on the source, destination and intended next step. We agree the files, structure, naming and any accompanying reports during discovery.
Is delivery to storage the end of the migration?: It can be, or it can be an agreed staging step. The statement of work defines who owns the data and next action after handover.

Learn about Global Relay migrations · Learn about SFTP migrations