---
title: "How to Export Data from Maximizer CRM: Methods & Limits"
slug: how-to-export-data-from-maximizer-crm-methods-limits
date: 2026-04-06
author: Raaj
categories: [Maximizer CRM]
excerpt: "Learn how to export data from Maximizer CRM via CSV, XML, SQL .BAK, and the Octopus API — including attachment limits, rate throttling, and data model gaps."
tldr: Native Maximizer exports miss attachments and flatten relational data. The Octopus API caps at 100 calls/min. Complete migrations need custom extraction or specialist help.
canonical: https://clonepartner.com/blog/how-to-export-data-from-maximizer-crm-methods-limits/
---

# How to Export Data from Maximizer CRM: Methods & Limits


**There is no single "Export Everything" button in Maximizer CRM.** The built-in Import/Export/Transfer tool exports Address Book entries (companies and individuals) to CSV or tab-delimited files — and that is where its usefulness largely ends. Opportunities, cases, leads, and calendar data each require a different extraction path. Documents and attachments are stored as binary blobs in SQL Server and are **not reliably exportable through any native UI function**.

If your goal is a **complete, migration-ready extract** — to move to Salesforce, HubSpot, Zoho, or another modern CRM — you need to understand exactly what each method gives you, what it leaves behind, and where it breaks.

**Migration-ready extract** means source IDs, owner assignments, timestamps, user-defined field values, file attachments, and relationship keys all preserved in a format the target system can ingest. A flat CSV of contact names and emails does not qualify.

If you are still tempted to run a CRM move from spreadsheets alone, read [Using CSVs for SaaS Data Migrations](https://clonepartner.com/blog/blog/csv-saas-data-migration/).

| Method | Format | Best For | Major Limits |
|---|---|---|---|
| **Native CSV/Tab Export** | CSV, TSV | Quick Address Book pulls | Companies and Individuals only; no Contacts, opportunities, or documents |
| **Native XML/MXI Export** | XML | Richer Address Book pulls | Can include Contacts and documents, but contact unique IDs are not exported |
| **Excel/Report Export (Web)** | XLSX | Audits and on-screen list pulls | Current column setup only; static snapshot |
| **Calendar Sharing** | ICS | Publishing appointments | Calendar only; not a migration tool |
| **SQL .BAK Backup (On-Prem)** | SQL Server backup | Full on-prem data preservation | Not importable by any modern CRM; requires SQL Server to restore |
| **Octopus API** | JSON + binary download | Full programmatic extraction | Rate throttling; POST-based reads; requires custom scripting |
| **Ferret API v2** | JSON | Simpler read-only pulls | Beta; narrower object coverage; page size 1–100 |
| **Webhooks** | JSON events | Delta sync after baseline | 10 targets per instance; 2-second response requirement; not a backfill tool |

## Quick Answer: How to Export Contacts via CSV

This is the path most Maximizer users try first. It works for a basic contact pull. It fails for anything migration-scale.

### Step-by-step (Desktop Client)

1. <cite index="6-22,6-23,6-24">Click the **Maximizer button** (multi-colored hexagon) at the top left of your screen. In older versions, select **File**. Navigate to **Import/Export/Transfer** → **Address Book Entries**.</cite>
2. <cite index="6-25,6-26">Click **Browse** to choose a save location and file name. Set the format to **Comma Separated Value (CSV)**.</cite>
3. <cite index="6-27">Select the fields you want to export. Double-click each field or click **Add** to include it.</cite>
4. <cite index="6-28">Click **Export** to generate the CSV file.</cite>

> [!WARNING]
> **Notes with commas or tabs inside them will corrupt your CSV.** The native exporter does not escape delimiters within note text. Inspect the output before feeding it into any import tool.

### What this gives you

- Company and Individual Address Book entries
- Phone numbers, email addresses, physical addresses
- User-defined fields (UDFs) you explicitly select — but not table UDFs with multiple items, and not encrypted UDFs
- Notes (if selected — with delimiter risk)

### What this does NOT give you

- **Contacts** (sub-entries under Companies) — CSV/tab export covers Companies and Individuals only. XML can include Contacts. ([download.maximizer.com](https://download.maximizer.com/MaxV12entrepreneur/V12Entrepreneur_Docs/MaxCRMAdminGuide-Entre.pdf))
- Opportunities, leads, or cases
- Documents or file attachments
- Calendar entries or hotlist tasks
- Relational keys linking records to parent companies
- Interaction history

<cite index="9-7">You must have the "Allow export" privilege to use the export commands.</cite> <cite index="10-8,10-9,10-10,10-11">Some Maximizer versions (e.g., 10.5) only allow CSV export for companies, not contacts. You can export companies, contacts, and notes in XML format as an alternative.</cite> Check your version before assuming CSV covers everything.

## The Core Methods to Extract Maximizer Data

### Method 1: Native CSV / Tab / XML Export (Desktop Client)

**Best for:** Quick one-time Address Book pulls under a few thousand records.

CSV and tab-delimited formats export **Companies and Individuals** from the Address Book. They do not export Contact sub-entries, opportunities, cases, leads, documents, or interaction logs. Table UDFs with more than one item are unsupported in CSV/tab output, and encrypted UDFs cannot be exported. ([download.maximizer.com](https://download.maximizer.com/MaxV12entrepreneur/V12Entrepreneur_Docs/MaxCRMAdminGuide-Entre.pdf))

**XML/MXI export** is the richer native option. According to Maximizer's admin guide, XML can optionally include Contacts, opportunities, Address Book UDFs, notes, documents, and Unicode output for non-English characters. It is still Address Book-centric, not a whole-instance dump. ([download.maximizer.com](https://download.maximizer.com/MaxV12entrepreneur/V12Entrepreneur_Docs/MaxCRMAdminGuide-Entre.pdf))

A migration-critical caveat: unique IDs are exported for Companies and Individuals, but **contact unique IDs are not exported in XML**. That makes XML better than CSV for completeness but still problematic if your target system depends on stable contact-level identifiers. ([download.maximizer.com](https://download.maximizer.com/MaxV12entrepreneur/V12Entrepreneur_Docs/MaxCRMAdminGuide-Entre.pdf))

### Excel / Report Export (Web App)

The web client's Excel export pulls selected entries from the active page using the current column setup. Report templates are available for Address Book, Opportunities, Customer Service, Campaigns, and Hotlist. These exports are static snapshots — useful for auditing and user review, not for full-fidelity migration. ([support.maximizer.com](https://support.maximizer.com/hc/en-us/articles/23134384982541-about-export-to-excel))

### Calendar Sharing

Appointments use a separate path. Maximizer's Calendar Sharing feature publishes events in **.ics** format for Google Calendar, Outlook, and Apple Calendar. Useful for publishing schedules; not a migration tool for historical CRM activity. ([support.maximizer.com](https://support.maximizer.com/hc/en-us/articles/23136360550669-Calendar-Sharing))

### Method 2: SQL Server .BAK Backup (On-Premise Only)

**Best for:** Full data extraction when you have direct server access.

<cite index="7-10,7-11,7-12,7-13,7-14,7-15">On-premise Maximizer installations store data in Microsoft SQL Server. Each address book has its own database.</cite>

A `.BAK` backup is the most complete extraction path for on-prem users. Maximizer offers two backup modes: **Regular Backup** (requires the Address Book to be closed) and **Quick Backup** (can run against an open Address Book). Both create `.BAK` files containing the majority of Maximizer data, though custom dictionary and holiday files are excluded. ([download.maximizer.com](https://download.maximizer.com/MaxV12entrepreneur/V12Entrepreneur_Docs/MaxCRMAdminGuide-Entre.pdf))

> [!NOTE]
> **No modern CRM imports `.BAK` files directly.** You must restore the backup to a SQL Server instance, then write queries to extract and transform the data. Zoho's own Maximizer migration guide confirms this — it expects CSV, while Maximizer exports arrive as `.BAK`.

The key tables to know:

- **AMGR_AbEntries** — Address Book entries (companies, individuals, contacts)
- **AMGR_Opportunity** — Opportunities and deals
- **AMGR_Notes** — Notes attached to entries
- **AMGR_Letters_Tbl** — Documents and email attachments (binary encoded)
- **AMGR_UDF** — User-defined field values

<cite index="7-2">Once the data is loaded, you can export tables using SQL queries in Management Studio to join views and tables and export the data to CSV.</cite>

For a migration-ready extract, you need JOIN queries that reconstruct parent-child relationships between companies and contacts, and between entries and their associated opportunities, notes, and documents.

> [!WARNING]
> If your Maximizer environment uses **linked documents** or **hyperlinks**, plan a separate file-system capture. Maximizer can store documents embedded in the database, linked via UNC paths, or as hyperlinks to external files. Only embedded documents live inside the `.BAK` backup. ([download.maximizer.com](https://download.maximizer.com/MaxV12entrepreneur/V12Entrepreneur_Docs/MaxCRMAdminGuide-Entre.pdf))

Before starting any database-level extraction, audit your data and plan your field mapping. Our [data migration checklist template](https://clonepartner.com/blog/blog/data-migration-checklist-template/) covers the preparation steps most teams skip.

### Method 3: Octopus API (Cloud & On-Premise)

**Best for:** Programmatic extraction of structured data including contacts, opportunities, leads, cases, notes, and tasks.

<cite index="12-1,12-2">Octopus API (also known as Maximizer.Web.Data) is a web service API that provides access to Maximizer CRM data in JSON format. You can access your Maximizer CRM data from any web application, desktop application, or mobile app.</cite>

Authentication uses a **Personal Access Token (PAT)**. <cite index="20-43">On-premise customers should use their domain URL as the endpoint, rather than `api.maximizer.com`.</cite>

> [!TIP]
> Create a dedicated **read-only service user** and issue the PAT for that user, not for a human admin. Maximizer's PAT documentation explicitly describes this as a security best practice. ([developer.maximizer.com](https://developer.maximizer.com/v1.6/docs/personal-access-token))

The API exposes endpoints for Address Book entries, opportunities, leads, cases, notes, hotlist tasks, calendar appointments, interaction logs, and documents. This is the only method that gives you structured access to all major object types without direct database access.

**Non-obvious constraint: reads are POST-based, not GET-based.** Maximizer's Power BI integration guide calls this out explicitly. If your ETL tool assumes GET-only reads, expect custom work. ([developer.maximizer.com](https://developer.maximizer.com/docs/maximizer-and-powerbi))

A practical baseline extraction pattern:

```bash
# Baseline object export
POST /octopus/Read

# Persist stable source references
store: ID + Number   # not Key.Value

# Document binaries
GET /octopus/BinaryDownload/{document-key}
```

For any record you plan to reconcile later, store the invariant **ID + Number** pair, not the transient `Key.Value`. Maximizer's documentation states that Keys are not guaranteed to remain stable across sessions, servers, or versions, while `ID` and `Number` are the stable external reference pair. ([developer.maximizer.com](https://developer.maximizer.com/reference/octopus-api-docs-field-and-object-types-key))

UDFs require special handling in the API. Complex table structures do not return as simple key-value pairs — you receive nested arrays of UDF definitions that must be mapped back to the core Address Book entry ID.

**Ferret API v2** also exists as a read-only alternative with a narrower object surface. Maximizer's developer docs describe it as beta and recommend Octopus when you need broader functionality. Ferret paginates with a PageSize of 1–100 and a NextPageKey loop. ([developer.maximizer.com](https://developer.maximizer.com/reference/ferret-api-getting-started))

## Octopus API Rate Limits & Webhook Constraints

### Rate Throttling

The rate limits depend on which documentation you reference. The Microsoft Power Platform connector lists **100 API calls per connection per 60 seconds**. ([learn.microsoft.com](https://learn.microsoft.com/en-us/connectors/maximizercrm/))

Maximizer's own Ferret/Octopus developer documentation publishes edition-based limits that may be tighter:

| Edition | Requests per Minute | Max Request Duration |
|---|---|---|
| Base | 30 | 10 seconds |
| Sales Leader / Financial Advisor | 90 | 30 seconds |
| Enterprise / Private Cloud | Custom | Custom |

([developer.maximizer.com](https://developer.maximizer.com/reference/ferret-api-getting-started))

If you have 50,000 Address Book entries and each requires a separate API call plus pagination, you are looking at 8+ hours of continuous extraction at the connector's maximum throughput — before accounting for retries, errors, or document fetches. At the Base edition's 30 requests/minute, it takes significantly longer.

Exceeding these ceilings triggers `429 Too Many Requests` or `408 Request Timeout` responses. A naive script without proper backoff will silently drop records. You need explicit rate-limiting with exponential backoff built into any extraction script.

For a deeper look at why migration scripts cause silent data loss, see [The Data Migration Risk Model: Why DIY AI Scripts Fail](https://clonepartner.com/blog/blog/why-ai-migration-scripts-fail/).

### Webhook Constraints

Maximizer's webhook system pushes real-time notifications when records are created or updated. The hard constraints:

- **10 webhook targets per instance** — if you need sync to multiple downstream systems, you run out of slots fast
- **Organization-level only**, admin-managed
- **Targets must return 200 OK within 2 seconds** — Maximizer retries twice, then permanently discards the event

([developer.maximizer.com](https://developer.maximizer.com/docs/webhooks))

Webhooks are designed for **ongoing delta sync after a baseline export**, not for historical backfill or bulk extraction.

## The Attachment Problem: Why Native Exports Leave Files Behind

This is where most Maximizer migration projects stall.

<cite index="22-1,22-2">Documents are stored in a blob object and you cannot export them.</cite> The native CSV, tab, and XML exporters extract text fields — document references, file names, metadata — but **not the actual file contents**.

<cite index="21-1,21-2,21-3,21-4">In the Maximizer database, the `AMGR_Letters_Tbl` table stores documents and emails with attachments. The `TextCol` column in the letters table is of type `image` containing encoded data.</cite>

<cite index="21-6,21-7,21-8,21-9">It is quite difficult to extract documents from Maximizer, and exporting emails with attachments is even more difficult. Specialized services provide a folder structure filled with documents and an accompanying Excel/tab file containing the data, filepath, and IDs for each document.</cite>

The storage model adds complexity. Maximizer documents can be **embedded** in the database as binary blobs, **linked** via UNC paths to files outside the database, or stored as **hyperlinks** to external locations. Each type requires a different extraction approach. ([download.maximizer.com](https://download.maximizer.com/MaxV12entrepreneur/V12Entrepreneur_Docs/MaxCRMAdminGuide-Entre.pdf))

In the Octopus API, a Document is a reference to a stored binary. The API provides a dedicated **BinaryDownload** endpoint for the actual file payload. Attachment migration is always at least a two-step job: export the document metadata records, then download the binaries — while respecting rate limits. ([support.maximizer.com](https://support.maximizer.com/hc/en-us/articles/23137827090189-Documents))

If your Maximizer instance contains Word documents, PDFs, email attachments, or scanned images attached to records, **none of them will appear in your CSV export**. You need either:

1. **Direct SQL Server access** to query `AMGR_Letters_Tbl`, decode the blob data, and write the files to disk
2. **The Octopus API** to iterate through entries and download binaries via the BinaryDownload endpoint
3. **A migration specialist** who has reverse-engineered Maximizer's internal binary encoding

There is no official Maximizer documentation describing the blob encoding format. This is reverse-engineering territory.

> [!CAUTION]
> Do not sign off on a Maximizer export after checking **row counts only**. Validate one company, one contact, one opportunity, one case, one note thread, and one document with a real binary file end-to-end. That single test catches most migration failures earlier than any spreadsheet audit.

## Data Model Mismatches: Maximizer's Flat Structure vs. Relational CRMs

Maximizer's data model is **Address Book-centric**. Everything revolves around a central Address Book that holds companies, individuals, and contacts. Opportunities, notes, and cases link to Address Book entries, but the relationships are flatter than what Salesforce, HubSpot, or Dynamics 365 expect.

<cite index="52-1,52-2,52-3">It is important to map the data model and fields from Maximizer to Salesforce at the start of the project as part of the design phase.</cite> Navirum's Maximizer-to-Salesforce guidance reinforces this: Maximizer's flat data model does not map directly to Salesforce objects, and some fields require entirely new objects in the target system. ([navirum.com](https://navirum.com/2023/03/02/4-tips-for-migrating-from-maximizer-to-salesforce/))

| Maximizer Concept | Salesforce Equivalent | HubSpot Equivalent | Migration Issue |
|---|---|---|---|
| Company (Address Book) | Account | Company | Straightforward |
| Individual (Address Book) | Contact or Person Account | Contact | Depends on B2B vs. B2C |
| Contact (sub-entry) | Contact (child of Account) | Contact (associated to Company) | Parent-child link must be preserved |
| Opportunity | Opportunity | Deal | Sales process stages may not map 1:1 |
| User-Defined Fields | Custom Fields | Custom Properties | Field types may differ (dropdowns, dates, booleans) |
| Notes | Activity/Note | Note/Engagement | Timestamps and owners must transfer |
| Documents (blobs) | Files (ContentDocument) | Files | Requires separate upload workflow |

The core problem: **Maximizer's flat CSV export does not include the keys that link contacts to their parent companies, or opportunities to their parent contacts.** Without those relational keys, your Salesforce import creates orphaned contacts with no account association and orphaned opportunities with no pipeline context.

If you are using the API, build a crosswalk keyed on Maximizer's stable **ID + Number** pair, plus separate mapping tables for company-contact parentage, owners/users, opportunities, and document parents. Row counts alone are not enough to verify a successful migration. ([developer.maximizer.com](https://developer.maximizer.com/reference/octopus-api-docs-field-and-object-types-key))

## DIY vs. Migration Tools

### Native Export + Manual Import

**Cost:** Free (your time excluded).

**Works for:** Small databases under 1,000 contacts with no attachments and no complex relationships.

**Fails when:** You need opportunities, documents, or notes with intact relational links. You will spend weeks in Excel running VLOOKUPs to stitch companies and contacts back together and manually uploading files one by one.

### Zapier / Power Automate

<cite index="36-7,36-8">Zapier lets you send info between Maximizer CRM and other apps automatically — no code required.</cite> Both platforms are useful for **ongoing operational sync** — triggering actions when a new lead is created, for example. They are not designed for bulk historical extraction. Running 20,000 contacts with 5 years of interaction history through Zapier one record at a time is neither practical nor cost-effective. The same rate-limit constraints apply through the Maximizer connector.

### SuprSwitch (Maximizer → HubSpot)

SuprSwitch by Suprdense is a dedicated migration tool for moving data from Maximizer CRM to HubSpot, handling users, objects, associations, properties, and customizations. ([suprdense.com](https://www.suprdense.com/switch/migrations/maximizer-crm-to-hubspot-data-migration)) If HubSpot is your target and your data model is conventional, it can save significant time compared to DIY. Validate its handling of attachments, unsupported custom logic, and edge cases before committing — it is purpose-built for one target platform.

### Migration Specialists

For complex migrations — especially those involving document extraction from binary blobs, custom field mapping across dozens of UDFs, and relational data reconstruction — a specialist team with direct Maximizer experience is the fastest path. This is especially true when the `.BAK` database contains encoded documents that require reverse-engineering.

For a broader comparison of migration approaches, see our guide to the [Top 5 Best CRM Migration Solutions](https://clonepartner.com/blog/blog/top-5-best-crm-migration-solutions/).

## Pre-Export Checklist

Before you pull a single record out of Maximizer:

- [ ] **Check your deployment type.** On-prem (SQL Server access available) vs. cloud (API-only) changes your extraction options entirely.
- [ ] **Inventory your data types.** List every record type you need: Address Book entries, opportunities, leads, cases, notes, documents, calendar items, interaction logs, campaigns.
- [ ] **Count records per type.** This determines which extraction method is viable and how long API extraction will take at your edition's rate limit.
- [ ] **Identify user-defined fields.** Document every UDF name, type, and possible values. Table UDFs and encrypted UDFs have export restrictions in CSV/tab formats.
- [ ] **Audit document storage.** Determine whether your documents are embedded in the database, linked via UNC paths, or stored as hyperlinks. Plan a separate extraction workflow for each type.
- [ ] **Map your target data model.** Define how Maximizer's Address Book entries, opportunities, and cases map to your target CRM's objects before you start exporting.
- [ ] **Test a small export first.** Run the CSV or API export on a filtered subset of 50–100 records. Verify the output includes every field you need, in the format you expect — and validate at least one real document with its actual binary file.

For a complete preparation framework, use our [data migration checklist template](https://clonepartner.com/blog/blog/data-migration-checklist-template/).

## How ClonePartner Handles Maximizer Migrations

The Maximizer projects that go sideways usually look fine at first glance. The CSV opens. The backup restores. The API returns JSON. Then the real problems surface: linked files were never copied, custom fields lost context, contact-to-company relationships were rebuilt incorrectly, or the export script silently stopped at rate limits and nobody noticed.

We have done enough Maximizer extractions to know these failure modes. The three problems that trip up every DIY attempt:

1. **Blob-encoded documents** that no native export touches. We extract the actual files from `AMGR_Letters_Tbl`, decode them, and deliver them as a structured folder hierarchy with a lookup index. For API-based extractions, we handle the BinaryDownload endpoint with built-in rate limiting.
2. **The API throttle ceiling.** Our extraction scripts include adaptive backoff so we pull every record without hitting 429 errors or silently dropping data.
3. **The flat-to-relational transformation.** We preserve Maximizer's internal identifiers and use them to rebuild parent-child relationships (Company → Contact, Entry → Opportunity, Entry → Note) in the target CRM.

We use a delta-sync approach so your team keeps working in Maximizer while we migrate historical data, capturing final changes right before go-live. We handle Maximizer → Salesforce, Maximizer → HubSpot, Maximizer → Zoho, and custom targets.

> Need to get your data out of Maximizer CRM — including the attachments and relational links that native exports leave behind? Book a free 30-minute technical scoping call and we'll map out your migration.
>
> [Talk to us](https://cal.com/clonepartner/meet?duration=30&utm_source=blog&utm_medium=button&utm_campaign=demo_bookings&utm_content=cta_click&utm_term=demo_button_click)

## Frequently asked questions

### How do I export contacts from Maximizer CRM to CSV?

In the desktop client, click the Maximizer button → Import/Export/Transfer → Address Book Entries. Choose a file location, set the format to CSV, select your fields, and click Export. Note that CSV/tab export covers Companies and Individuals only — not Contact sub-entries. For Contacts, use XML export or the Octopus API.

### Can I export documents and attachments from Maximizer CRM?

Not through native export tools. Documents are stored as binary blobs in the AMGR_Letters_Tbl table or as linked/hyperlinked files outside the database. You need direct SQL Server access, the Octopus API's BinaryDownload endpoint, or a specialized extraction tool to retrieve the actual file contents.

### What are the Maximizer CRM API rate limits?

The Microsoft Power Platform connector enforces 100 calls per 60 seconds per connection. Maximizer's own developer documentation publishes edition-based limits: 30 requests/minute for Base, 90 for Sales Leader/Financial Advisor, and custom limits for Enterprise. Exceeding these triggers 429 or 408 errors and can cause silent data loss.

### How do I migrate data from Maximizer CRM to Salesforce or HubSpot?

Extract contacts via CSV or the Octopus API, then map Maximizer's flat Address Book model to the target's relational objects (Accounts and Contacts in Salesforce, Companies and Contacts in HubSpot). Documents require separate extraction. The data model mapping — preserving parent-child relationships and UDFs — is the most complex and failure-prone step.

### Does Maximizer CRM support full database backups?

On-premise installations store data in SQL Server. You can create a .BAK backup using Regular or Quick mode, but no modern CRM imports .BAK files directly. You must restore it to a SQL Server instance and query the tables to extract data into CSV or JSON for your target system.