What you can export from Marketo before your contract ends
Lead and person records are the part of a Marketo Engage account you can take out in bulk. The Bulk Lead Extract REST API returns large sets of lead and person records as CSV, TSV or SSV files, and each job can cover a date range of 31 days or fewer, so a full history takes several jobs. Smart campaigns, assets and other configuration have no bulk export, so you must document them by hand or rebuild them elsewhere. Marketo Engage is part of Adobe Experience Cloud, and your export rights and data terms sit in your Adobe agreement, so confirm them before you plan the work.
Treat the export as a data task, separate from rebuilding campaign logic. Activities, program members and custom objects come through their own Bulk Extract jobs with their own limits, so decide which ones you need for reporting, suppression and audit before you request anything. Adobe's documentation sets a 500 MB daily quota and 7-day file retention, which means a large account may need to spread its pulls across several days, and any file you do not download in time expires. Ask your Marketo administrator to check current limits in the Bulk Lead Extract documentation and to confirm the API user's permissions and quota usage.
Decide what leaves the account and where it lands before the subscription ends. Write a retention rule for each record type, and keep the consent and unsubscribe fields so suppressed contacts are not re-imported into Mautic. Record a row count for each file so you can show that every batch arrived complete. Keep the Marketo instance running through the full extract window, because a closed instance cannot be queried again. Store the files in encrypted storage that you control, and confirm with your legal and privacy team that moving personal data into your own infrastructure matches your processing records.
Marketo data types, export methods, formats and limits
This table lists each Marketo data type you may need to move, the export path Adobe provides for it, and the formats and limits that apply. Read the second and third columns together, then confirm each row against your own instance and Adobe's current documentation before you plan a job schedule.
| Data type | Export path | Formats and limits |
|---|---|---|
| Lead and person records | Bulk Lead Extract REST API | CSV, TSV or SSV files; date range filter of 31 days or fewer per job |
| Activities | Bulk extract for activity records (confirm endpoint and filters) | Confirm the maximum date window per job and the output format in Adobe's bulk extract docs |
| Program members | Bulk extract for program member records (confirm endpoint) | Confirm supported formats, date filters and whether program membership is exported as a separate job |
| Custom objects | Bulk extract for custom object records (confirm endpoint) | Confirm object-level permissions, supported formats and any per-job limits for your instance |
| Daily export quota | Applies across bulk extract jobs in the instance | 500 MB per day; confirm how Adobe measures usage and when the quota resets |
| File retention | Downloaded export files on Marketo's side | 7 days; download and store files in your own system before they expire |
| Smart campaigns and assets | No bulk export in this scope | Document in the user interface or rebuild in the target platform; confirm current options with Adobe |
What Marketo does not export in bulk and how to capture it
Bulk Lead Extract covers lead and person records, but a Marketo account also holds configuration that explains how that data was created and used. No documented bulk export path covers smart campaigns, assets, scoring models or reports. Plan a capture method for each item before your subscription ends, and confirm each one with Adobe.
Smart campaigns and flows
Smart campaigns hold the triggers, filters, wait steps and choices that moved a lead through a nurture. Bulk Lead Extract returns the lead records and not the logic that decided where each record went. Export campaign membership and activity history, then write each trigger, filter and branch into a specification. Treat this as a no bulk export path item until Adobe confirms otherwise.
Email, landing page and form assets
Emails, landing pages and forms hold the copy, templates, merge fields and form logic that prospects actually saw. Bulk Lead Extract does not return any of them. Capture each live asset by saving rendered HTML and screenshots from the Marketo UI, and record form fields, hidden fields and thank-you actions in a sheet. Confirm which asset types the UI can export and in what format, since your user permissions shape what you can see.
Lead scoring models
Scoring models set the points for each activity and the thresholds that triggered sales handoffs. Activity exports show what a lead did, but not the weights applied to each action. Export a sample of scored leads with their current scores, then reconstruct the rules by checking which activities explain each score. Keep the thresholds and the dates each rule changed, because past scores cannot be recalculated without them.
Reports and dashboards
Reports and dashboards calculate figures from data that stays inside Marketo. A CSV of leads does not reproduce a report's filters, date logic or attribution model. Save the definition of every report that sales or finance relies on, export the underlying figures for the periods you must keep, and label each file with the filter used to produce it. Ask Adobe whether report definitions have any export or API path under your subscription.
Users, roles and admin history
User roles, API service accounts and administrative changes shape who could touch data and when. These records matter when an auditor or a data subject asks who changed a campaign or accessed a record. List users and roles from the admin pages, document each API service account and its permissions, and confirm how far back the audit history can be retrieved and whether any export includes it.
The export sequence and how to verify each file
This sequence moves Marketo data from a written extract plan to a verified, checksummed archive in your own storage. Each batch passes checks before the next one starts, and the final checklist shows what was exported and what needs separate handling.
Inventory the instance and define date windows
The export owner, usually a marketing operations lead with admin access, lists every object to extract: leads, activities, program members and any custom objects. For each object, record the field list, the date range that must be covered and the expected record count from Marketo reporting or a manual count confirmed with your admin. The full history is then split into date windows of 31 days or fewer. The output is a written extract plan that names each job, its window and its owner, so no gap or overlap appears later.
Submit Bulk Lead Extract jobs in 31-day slices
A developer or admin creates each job through the Bulk Lead Extract REST API, setting the date filter to one window of 31 days or fewer and choosing CSV, TSV or SSV output. Before submitting, confirm in Adobe's bulk documentation which endpoint and filters apply to leads, activities, program members and custom objects, since each may differ. Submit slices in the order of the plan. The output is a job log entry for every slice, recording the job ID, object, window, format and status, including slices that return no records.
Track each job against the daily quota
After each submission, the operator checks job status and the volume returned, so that the day's exports stay within the 500 MB daily quota. Heavier windows are spread across several days in the plan rather than run together. Ask Adobe or your admin how quota usage is reported in your instance, because the figure shown in the interface is the one your planning should follow. The output is a daily quota ledger showing volume exported each day and the volume remaining for the next run.
Download every file before retention ends
Each completed file is downloaded to a staging location as soon as it becomes available, because Marketo keeps extract files for 7 days. A named operator reviews the job log daily and flags any completed job whose file has not yet been downloaded. Confirm with Adobe whether the 7-day retention counts from job creation or job completion, and plan around the earlier date. The output is a local copy of every completed file, stored with the download time and source job ID.
Verify each batch on arrival
Each file is opened as soon as it lands and checked for completeness. The header must match the field list from the plan, the delimiter must match the format requested, the character encoding must read cleanly, and the file must end on a complete record with no truncated row. A file that fails any check is marked failed in the log and its slice is re-run before the window is closed. The output is a pass or fail result for every file, with the reason recorded for each failure.
Store files with checksums and a manifest
A SHA-256 checksum is calculated for each passing file, and a manifest is written listing the file name, object, date window, job ID, record count, checksum and download time. The files and manifest are copied to write-protected storage inside your own infrastructure, and the checksums are recalculated on the copy to confirm it matches. Retention periods for the archive should be agreed with your compliance owner. The output is a verified archive with a manifest that lets anyone reconfirm each file later.
Reconcile counts and key fields against Marketo
The row count in each file is compared with the count Marketo reports for the same object and window, and a sample of lead IDs and email addresses is checked against the source records. Records changed during an export can appear in two adjacent windows, so the deduplication rule for boundary records is agreed before reconciliation and written into the plan. Each variance is explained in the reconciliation sheet. The output is a reconciliation sheet per object that shows matched counts, explained variances and the rule applied to boundary records.
Sign off with a final checklist
The migration lead and the data owner review a final checklist before any source data is retired. The checklist confirms that every planned window has a verified file and a manifest entry, that all checksums match the stored copy, that the quota ledger and retention log are complete, and that every reconciliation variance has an explanation. Smart campaigns and assets have no bulk export, so they are listed separately with their documented handling. The output is a signed sign-off record that becomes part of the migration file.
How the exported files land in a self-hosted target
The CSV, TSV or SSV files from Bulk Extract are not directly importable into Mautic without preparation, but the format is close enough that the work is mostly column review. Mautic's CSV import maps columns to contact fields automatically when the header names match its field aliases, and anything unmatched has to be mapped by hand. Before you start, extract a small test file, open it in Mautic's import screen, and check every header. Confirm that the delimiter you chose during extraction matches what Mautic expects, because a mismatched TSV or SSV file will often import as one unreadable column rather than failing outright.
For anything beyond a few thousand rows, the Mautic project recommends running the import in the background with the mautic:import console command, scheduled through cron. Imports are processed in batches of 100 rows by default, so the batch size and the time the job needs are worth measuring on your test file before you schedule the full run. Plan a reconciliation step after the import: compare row counts in the source extract against the contacts created in Mautic, and check that the email address is set as the unique identifier so duplicates merge instead of multiplying.
Imported contacts are not yet usable for marketing. Each consent and subscription status must be mapped deliberately, because a Marketo export does not carry a guarantee that the legal basis for each contact carries over into Mautic. Confirm with your legal or privacy team which fields prove consent, and map only those. Historical activity records also rarely map one to one. Marketo activity types, program membership and scores have their own structures, so expect to store some history as custom fields or notes, and to decide with stakeholders which history is worth carrying forward at all.
What to plan before the Marketo renewal or termination date
Extraction is the slowest part of leaving Marketo, and it depends on contract dates you control only partly. The cards below cover the sequence, the access you need to keep, the records you must retain, and the contract terms to confirm with Adobe before the subscription ends.
Work back from the contract end
Set the extraction schedule from the termination date, not the other way round. Bulk Extract works in date windows of 31 days or fewer per job, and the daily quota and file retention limit how fast you can pull history. Map every object you need, then count the jobs and days each one takes. Start with the oldest data so that recent activity can be exported last, close to the cutover.
Keep Marketo access until exports finish
Ask Adobe in writing whether your admin and API access continues through the final export window, and for how long after the contract end. Confirm which user roles and REST API credentials stay active. If access ends early, you lose the ability to re-run a failed job against Marketo, which is the only source for the data. Plan a final full pull before access is revoked and keep a second copy of each file.
Retain archives for legal and audit needs
Decide which exported records you must keep for legal holds, tax, audit trails and regulatory inquiries about past campaigns. Lead and activity files contain personal data, so define retention periods with your legal and compliance teams rather than copying defaults from a tool. Store archives in encrypted, access-controlled storage with a documented owner, and test that you can still read the CSV or TSV files years later.
Carry over consent and suppression status
Export opt-out flags, email and subscription preferences, bounce and unsubscribe history, and the suppression lists alongside leads. Mailing a contact who opted out after the move creates a compliance problem that is harder to fix than a missed send. Confirm how each consent source is recorded in Marketo before you import anything into Mautic, and document the evidence trail for every contact you plan to email.
Confirm export rights and data return terms
Read the subscription agreement for clauses on data ownership, export format, data return and deletion after termination. Ask Adobe to confirm in writing what data it will provide on request, in what format and within what timeframe, and whether any fee applies. Also confirm when Adobe deletes your data. Keep the written answers in the project file, since a verbal assurance from a sales or support contact will not protect you in a dispute.
Plan the cutover and records of processing
Schedule a freeze window for new lead activity so the final delta export matches the Mautic import. Record which files were exported, when, by which job, and how many rows each contained, so you can reconcile counts after import. Update your records of processing to show where the data moved, who holds it, and how long the archive is kept. These records make the change easier to explain during a privacy review.
Common questions about exiting Marketo data
How much effort does a complete Marketo export take?
Effort rises with how much history you hold and how many separate extracts you must run. Bulk Lead Extract limits each job to a date range of 31 days or fewer, so long activity histories split into many jobs. The main drivers are:
- Record volume across leads, activities and program members
- The number of 31-day windows needed for activity history
- Custom objects, each needing its own extract and field mapping
- Field count and the cleanup the files need before loading
Most of the work is scripting, validation and file handling rather than clicking through the interface. Ask for record counts per object before agreeing a scope, because those counts set the number of jobs.
Can our marketing team export Marketo data without a partner?
Often yes for a small instance, if someone with API access can call the REST endpoints and handle job status, downloads and file storage. The skills needed are scripting the date windows, watching the daily quota, storing files securely and reconciling record counts after each download. Teams usually struggle in three places: long histories that need many jobs, custom objects with unusual relationships, and the time spent waiting on quota limits. A partner is worth considering when the history is large or when no engineer can be spared for the length of the extract. Before committing internal time, confirm with your Marketo administrator that the API client has the permissions the extract requires.
What internal staff are needed for a Marketo data export?
Marketing operations owns the content of the export: which objects matter, which fields are still in use, which records must stay out because of suppression or consent status, and final sign-off on reconciled counts. A security owner decides where the CSV, TSV or SSV files may sit, who can read them, how they are encrypted at rest and when they are deleted after loading into Mautic. Someone from IT or platform engineering provides the storage and the scheduled runner. Your Marketo administrator issues API credentials with the narrowest permissions the extract needs. Agree these roles before the first job runs, because Marketo keeps exported files for seven days and downloads cannot wait for a decision.
How long does a Marketo export take and why does the quota matter?
No fixed duration can be given here because it depends on record volume, history depth and your subscription's current limits. The constraint that matters most is the 500 MB daily quota for Bulk Extract, which caps how much data you can extract in one day. A large instance therefore spreads its work across several days, so plan the schedule in days rather than hours. Confirm the current quota for your subscription in Adobe's Bulk Lead Extract documentation. Because files are kept for seven days, download each one as soon as it completes, store it in your own location and check its record count against Marketo before the next batch starts.
Which Marketo data has no bulk export option?
Bulk Extract covers lead and person records and related data such as activities, program members and custom objects. It does not cover the logic and content around that data. Smart campaigns, smart lists, assets, emails, landing pages and forms have no bulk export path, so they must be documented from the Marketo interface and rebuilt in Mautic. Your Marketo administrator should list every asset type in use and confirm in Adobe's documentation which objects each endpoint supports, including whether scoring models and program structures have an export path. Treat that list as the rebuild backlog, because the data export alone will not reproduce how your campaigns behaved.
What should a partner include in a written export scope?
A written scope should name each object in the export, its date range, the expected record counts and the method used to reconcile those counts against Marketo. Ask for the destination format, a Mautic import plan and the storage and encryption method for each file. The scope should also state what is excluded, such as smart campaign rebuilds, landing pages and historical email content. Require a handover document covering scripts, runbooks and validation results. DeployOpen works on fixed scopes agreed in writing before work starts, so timelines, deliverables and acceptance checks belong in that document. Ask for a quote built from that scope.
Which file formats does a Marketo bulk export produce for Mautic?
Bulk Lead Extract returns lead and person records as CSV, TSV or SSV files, so the format decision mostly depends on the tool that loads the data. Mautic imports CSV through its user interface and maps columns to fields automatically. For large files, Mautic's documentation recommends a background import with the mautic:import console command, run by cron. Those imports process rows in batches of 100 by default, so a large file can take a long time to complete. Convert TSV or SSV to CSV in a controlled step, check delimiters and encoding, keep the original files untouched for audit, and test with a sample before the full load.
Where to confirm Marketo export limits and formats
Before you plan any extract, confirm the limits for your own Marketo Engage version in Adobe's documentation. Start with the Marketo Engage documentation on Adobe Experience League, then read the Bulk Lead Extract reference in the Marketo developer docs. The reference describes the date range filter of 31 days or fewer per job, and it states that lead and person records come back as CSV, TSV or SSV files intended for ETL, warehousing and archival. Those three properties determine how you slice the history, which file format your target system can load, and how many jobs the full migration will need. Write them down before you open a support ticket or estimate the work.
Check each figure against your own instance rather than relying on a general reading of the docs. The daily export quota and the number of days an exported file stays available for download are the two numbers most likely to decide your schedule, and you should confirm both in the current reference for your release instead of trusting older blog posts or forum threads. Also confirm which objects the Bulk Extract API covers for your subscription. The reference is written around lead and person records, so verify separately whether activities, program members and custom objects follow the same limits, formats and retention rules. Smart campaigns and assets should be checked too, because you need to know whether they have any bulk export path at all before you plan to rebuild them by hand.
Turn the confirmed limits into a short run record. Note the Marketo version, the API user's permissions, the quota and retention values with the page or ticket where you found them, and the date you checked. Then run one small test extract on a date range you can verify by hand, and confirm the row counts and file layout match what your import into Mautic expects. If a limit is unclear or missing from the docs, ask Adobe or your Marketo administrator to confirm it in writing. Those answers become the basis for an extraction schedule, and they make it much easier to compare the scope of any migration quote against the work your own environment requires.
How DeployOpen scopes and delivers a Marketo data exit
DeployOpen plans and delivers the export as a fixed-scope engagement inside your own infrastructure, so extracts, transfer and storage stay under your control from the first job to the final archive. We agree the scope, deliverables and timeline in writing before any extraction starts.
How we scope
- Inventory which Marketo objects you need: leads, activities, program members and any custom objects.
- Confirm the date ranges required, since each Bulk Extract job covers 31 days or fewer.
- Agree the daily quota plan, the 7-day file retention window and the destination storage in writing.
How we build
- Build the extraction scripts against the Bulk Lead Extract API and related bulk endpoints in your environment.
- Set up the staging database and file storage inside your own cloud account or data center.
- Test the job schedule and file validation on a sample date range before the full history run.
How we hand over
- Document each extract job, its date range, row counts and checksums so the data can be audited later.
- Deliver a runbook covering re-runs, failed jobs and how to resume within the quota window.
- Provide an inventory of what was not exported, such as smart campaigns and assets, with recommended rebuild notes.
How we support
- Ongoing support, upgrades and continuous testing are available as a retainer after handover.
- Support can cover follow-up extracts if teams find gaps after the first full run.
- Confirm the support terms and response expectations in the written scope before work begins.
