How do I sync FTP data to Databricks?

Sign up for Weld, connect FTP as a source and Databricks as a destination. Weld handles the extraction, loading, and lets you transform data using SQL or dbt.

What FTP data can I sync to Databricks?

You can sync the objects the FTP connector exposes. The available objects depend on your FTP account permissions and configuration.

How often does Weld sync data from FTP?

Sync frequency depends on your Weld plan. Schedules range from every 5 minutes to daily intervals. Each sync processes only new and changed data.

Can I transform FTP data before it lands in Databricks?

Yes. Weld supports SQL-based transformations in the platform and integrates with dbt Cloud. You can clean, join, and model your data before analysis.

Is the FTP to Databricks integration secure?

Yes. Weld encrypts all data in transit and at rest, is SOC 2 Type II certified, and supports IP whitelisting. Credentials are stored encrypted and never logged.

FTP to Databricks integration

Connect FTP to Databricks and automatically sync your file storage data. Weld extracts data from FTP, loads it into Databricks, and lets you transform the data using SQL or dbt, no custom scripts required.

Start for free View setup guide

4.8 on G2

Source

Weld

Warehouse

Weld · New sync

SourceFTPConnected

Tables to sync

Your own tables, picked when you set up the sync.

Extract
Load
Keep in sync

DestinationDatabricksReady

ftp schema

ftp.Synced
ftp.Syncing
ftp.Synced
ftp.Synced

Trusted by data and AI teams

How it works

How to set up FTP to Databricks in Weld.
In the app, with the API or an agent.

Setup guide API guide MCP docs

Weld · New FTP sync

New connectionFTPAuthorised

Connection nameftp

AuthorizeOpens FTP to grant read access

Use cases

Why sync FTP to Databricks?
Ready for analysis.

Centralizing your FTP data in Databricks lets you join it with other data sources for cross-platform analytics and deeper insights.

Build reliable dashboards and reports by querying FTP data directly in Databricks using SQL or your preferred BI tool.

Centralized data warehouse
Bring FTP data into Databricks alongside other sources to create a single source of truth for your organization.
Automated reporting
Replace manual exports and spreadsheet-based reporting with automated pipelines from FTP to Databricks. Connect BI tools like Looker, Metabase, or Power BI.

Data

What data can you sync?
From FTP to Databricks.

Weld syncs the objects the FTP connector exposes into Databricks, and you choose which tables and fields to include. The connector's docs list what is available.

Weld MCP server

Ask your agent.
It queries Databricks for you.

Connect Claude, Cursor, ChatGPT or your own agent to Weld over MCP. It reads the FTP context, finds the tables it needs and runs the query in Databricks.

Set up the MCP server

Claude CodeOpus 5

ConnectedWeld MCP

Which FTP tables do we have in Databricks, and which is the largest?

Looking up what Weld has synced from FTP.

●weld·search_available_references

⎿raw.ftp.*

tables, columns and freshness

●weld·get_reference_schema

⎿columns, types and nullability

●weld·run_query

⎿select count(*) from {{raw.ftp.…}}

submitted

●weld·get_query_status

⎿DONE

●weld·get_query_result

⎿rows returned

✓Answered from FTP data in Databricks

>Ask about your FTP dataMCP

Under the hood

Technical considerations.
What to expect.

Incremental syncing: Weld uses incremental syncing where supported by the FTP API, loading only new and updated records to minimize data transfer and warehouse costs.
Schema handling: Weld automatically manages schema changes. If FTP adds new fields, they're detected and added to the corresponding Databricks tables.
Data freshness: Sync frequency depends on your Weld plan. Most connectors support schedules from every 5 minutes up to daily intervals.
Security: All data is encrypted in transit (TLS) and at rest. Weld is SOC 2 Type II compliant and supports IP whitelisting for database connections.

Resources