How to get your data out of LeedFox and how to switch to another provider or to your own infrastructure under Regulation (EU) 2023/2854 (the Data Act). The contractual rules for switching are set out in Article 18 point 5 of the Terms of Service. We update this page when the export formats or structure change.
1. Switching procedure
- You start the switch by a request in the app or by e-mail to support@leedfox.com. State whether you are switching to another provider (and which), to your own infrastructure, or are requesting only deletion of the data.
- The notice period for starting the switch is 2 months from delivery of the request.
- We carry out the switch within 30 calendar days after the notice period expires at the latest. During this time the service runs, you can export your data, and we give you reasonable assistance.
- After the transitional period ends, you have at least 30 calendar days to download the data, after which we delete the exportable data. It disappears from backups within 90 days at the latest.
- We charge no fees for the export or the switch.
2. Export methods
- List export: in the Leads or Contacts list, you download the displayed records to a CSV or Excel (XLSX) file, at most 5,000 rows in one file. The file contains the visible standard columns of the list and, for leads, all active custom fields. Column names are in the language of the app.
- Whole-account export: the account owner (the Owner role) prepares a ZIP archive with the account data in Settings → Data protection. The archive contains a CSV file and a JSON file with the same columns for each table, plus manifest.json and README.txt. We let you know when the archive is ready.
- API: through the REST API at app.leedfox.com/api/v1 you work with leads, their tasks and notes, and with the pipeline. The OpenAPI description of the interface is at app.leedfox.com/api/v1/openapi.json.
3. Formats and standards
- CSV: UTF-8 encoding with BOM, semicolon delimiter, CR LF line endings, quoting according to RFC 4180. An empty value is an empty cell; composite values (lists, objects) are written as JSON. Text that a spreadsheet could execute as a formula starts with an apostrophe.
- JSON: the same columns as the CSV, values unchanged (without the apostrophe for formulas).
- XLSX: the Office Open XML format (Microsoft Excel).
- Date and time: in the list export in the format
YYYY-MM-DD HH:mmin the account's time zone, a date alone asYYYY-MM-DD. - Relations and amounts: each record has an identifier
id, and relations between tables run through columns ending in_id(for examplelead_id). Amounts in columns ending in_minorare in the smallest currency units (cents), and rates and discounts in columns ending in_bpsare in hundredths of a per cent.
4. Data structures in the ZIP archive
| Area | Tables (files) | Main data |
|---|---|---|
| Account and company | workspace, company_profile | account name, language, time zone; the company's billing and contact details |
| Pipeline | pipelines, pipeline_stages | pipeline, stages and their order |
| Leads and contacts | leads, lead_field_folders, lead_field_definitions, lead_consents, lead_activities | contact details, company, source and UTM, stage, value, owner, custom fields and their definitions, consents (text, channels, legal basis, time granted and withdrawn), notes and activity history |
| Messages | messages, message_attachments | channel, direction, status, sender, recipient, subject, text; name, type and size of attachments |
| Bookings | bookings, booking_pages | time, status, contact, meeting link, notes; booking pages |
| Tasks | tasks, task_folders, task_sections, task_tags, task_checklists, task_checklist_items, task_links, task_attachments, task_activity, task_recurrences | tasks, folders, sections, tags, checklists, links, attachments (metadata), history and recurrences |
| Automations and templates | workflows, message_templates | description of automations (JSON), message templates |
| Requests | requests | type, status, content, response, deadlines |
| Files | proof_folders, proof_assets, proof_versions, proof_comments, files.csv, files.json | folders, metadata of files and versions, comments, links to files |
| Quotes | quotes, quote_lines | quotes, line items, VAT and totals |
| Reviews | review_links | Google and Facebook review links |
| Phone numbers | sms_numbers | assigned numbers, if you have any |
5. Known limitations
- Files: the archive contains a list of files with links into the app (files.csv, files.json), not their content. You download the files through these links for as long as you have access to the account.
- What the export does not contain: access tokens and passwords for integrations, encrypted and internal technical data (search indexes, storage keys, security settings), the account's users and their permissions, the change history (audit log) and source code. You connect the integrations (Meta, Google, Microsoft, Zoom) again at the new provider.
- Size and number: the ZIP archive is at most 50 MB; for a larger volume, write to support@leedfox.com and we will agree on a procedure. The whole account can be exported at most 5 times a day.
- Validity: the archive is available for 7 days; each download creates a new link valid for 5 minutes.
- List export: at most 5,000 rows in one file; split a larger list with a filter or use the whole-account export.
- Automations: they are exported as a description in JSON format; another system may not be able to load them directly.
6. Contact
Questions about export and switching: support@leedfox.com, technical questions: tech@leedfox.com.