ActiveCampaign pricing in Brazil: B2B migration

ActiveCampaign automates marketing campaigns and workflows. For 1,000 contacts, Starter begins at US$15 per month billed annually and permits up to five actions per automation; SSO appears in Enterprise. B2B teams should compare those limits, migration costs and a Brazilian-real proposal with a Brazilian tax invoice before signing. The cover image is a generated illustration; it does not depict a verified ActiveCampaign installation or imply its endorsement.

Key facts / Decision matrix: Use case: segment contacts and run B2B marketing campaigns and automations. Billing unit: contact tier, with a sending allowance and add-ons depending on the plan. Included users: one on Starter and Plus, three on Pro and five on Enterprise. Plan trigger: SSO appears in Enterprise; confirm other security requirements in the proposal. Contracting: consult ActiveCampaign on Nexforce Marketplace and request terms for the company's CNPJ, Brazil's company tax identification number.

The decision changes when a limit stops a task the team actually needs to perform. A small contact base with simple workflows can fit Starter; a requirement for SSO or more actions per automation changes the comparison even when the number of contacts stays small.

What does ActiveCampaign do in a B2B operation?

ActiveCampaign brings together contacts, fields, lists and tags to segment campaigns and trigger automations. A trigger starts a workflow, while actions determine what happens to each contact. Check the integration separately. APIs and webhooks connect the platform to other systems, but their inclusion does not establish the limits for every integration.

In practice, work starts with a contact record and its attributes. Marketing uses those details to build segments and decide who enters a campaign. In the builder, a trigger can start an automation that chains actions such as sending an email or updating information. For a B2B operation, the value appears when the workflow follows a rule the team can explain and review.

The architecture has boundaries. An integration relies on the field that feeds a segment, the rule that authorizes a send, the way data is updated and the person responsible for reviewing changes. If a source field changes meaning and nobody updates the workflow, an automation can stay active without reaching the intended audience. The automation builder documentation describes triggers and actions; confirm availability in the selected plan.

Image: ActiveCampaign automation builder.

How much does ActiveCampaign cost for 1,000 contacts?

For 1,000 contacts, ActiveCampaign pricing in US dollars starts at US$15 per month for Starter and reaches US$145 for Enterprise, billed annually. These are monthly equivalents. The official pricing table, consulted on November 11, 2026, does not present those amounts as an offer without an annual commitment.

The contact tier changes the price. These figures are starting points for the stated selection, not a quote for every contact base. They do not automatically include extra users, increased send allowances or migration services outside the confirmed scope. Unlimited actions on higher plans refers to actions per automation in the official table; it does not establish an unlimited number of automations.

The page selector offers Brazilian reais, but that choice alone does not confirm the final price for a CNPJ or the tax document issued for the purchase. For a larger contact base, the buyer should request a proposal for the actual tier and intended period before comparing contracting routes.

Which limits can change the plan choice?

The contact tier, send allowance, actions per automation and user access measure different things. Find the first constraint. A requirement for SSO, for example, points to Enterprise even when the contact base fits the entry tier, because the relevant limit is the one that prevents a required workflow.

Contacts and sends are different counts. For accounts created on or after November 3, 2025, all contacts count toward the limit, regardless of list status. For older accounts, the rule depends on the plan. The contact limit documentation also states that Starter supports up to 25,000 contacts.

When an account reaches its contact limit, the documentation says email campaigns stop sending until an upgrade. Contacts continue through automations but skip the email-send action. The vendor suggests considering auto-upgrade to prevent interruptions; the buyer should confirm how a tier change will be authorized and charged. Maintaining a suppression list is part of communication control, not a reason to delete records without checking the company's obligations.

The monthly send limit covers direct and automated campaigns, but not individual or transactional emails. If the allowance is exceeded without an increase, the overage documentation states a charge of US$0.005 per extra send and says service does not stop solely because the allowance is exceeded. It also describes sending being disabled until the next month when the amount of send overages reaches three times the limit, without clarifying the unit of that threshold. Confirm its application in writing. Under the stated rate, 1,000 extra sends equal US$5 if the rule applies to the account; this example does not predict a company's consumption.

There are costs beyond sends. Enhanced CRM add-ons are available from Plus, and WhatsApp has its own offer and limits. The pricing page includes API and webhooks on all four plans, but the team should confirm API limits, authentication, event volume and the behavior of required integrations. SSO appears in Enterprise; SCIM and data residency were not confirmed in this review.

AI credits also need a budget. The documentation states that 500 credits per month are shared across the account, do not roll over and can be supplemented with packs of 100 starting at US$10 per month. Advanced features can pause when credits run out; basic functions remain, with qualifications for scheduled tasks and specific AI actions. The documentation says reseller accounts are currently not subject to AI credits; confirm in writing whether that exception and the other rules apply to the contracted arrangement.

How should a team compare contracting and migration?

The comparison starts with the proposal. Record the plan and limits, calculate total cost for the same period and volume, inventory the assets that need to move, and release workflows only after testing the data, unsubscribe process and integrations. Keep transition costs visible. The sequence separates the subscription price from the work of moving.

1. Compare the plan, limits, proposal and total cost for the same period and volume.
2. Inventory data and workflows, then confirm the migration scope.
3. Test data, unsubscribe handling, automations and integrations before acceptance.

Step 1: How should a team compare ActiveCampaign costs in Brazil?

Compare the subscription, add-ons and migration for the same volume and period. With a direct purchase, confirm the billing currency and ask finance to validate any applicable charges; with a local proposal, check price, tax invoice, limits and services for the same period and use. Calculate after those terms are clear.

The quote must identify the contact tier and the number of users. Ask whether send expansion and integration work are included, since two proposals with the same plan name can still cover different work and leave different costs with the buyer.

Step 2: How should a team prepare an ActiveCampaign migration?

Migration begins with an inventory of data and workflows. Do not import yet. The team needs to know what will transfer, what must be rebuilt and who will approve each test; the proposal should identify included services and the cost of activities that remain with the buyer.

Before starting, bring together the owners of marketing, integrations and procurement, along with authorized access to the source data. The sequence produces a list of verifiable deliverables and keeps the subscription price separate from the full cost of transition.

1. Inventory the contact base: count contacts by status, lists, fields, tags and suppression records. Record the origin, purpose and owner of each set; ask the responsible team to verify the legal basis for migration and communication, and preserve consent records when consent is the applicable basis.
2. Map the assets: list campaigns, templates, forms, automations, triggers, actions and integrations. For each workflow, record its purpose and the data that determines a contact's entry or exit.
3. Confirm included migration: identify the eligible plan, covered objects, items to be rebuilt and the price or responsibility for work beyond the scope. Request a written answer.
4. Define tests: reconcile counts and statuses, validate unsubscribe handling, and set up deliverability, automation and integration tests before activating campaigns.
5. Plan the transition: record owners, activation order, any contract overlap and acceptance criteria. Decide how to return to the prior state if a critical test fails.

The onboarding page describes free migration of the first 10 objects on eligible plans, with lists, forms and automations among its examples. Qualify the offer for the account. Ask how an object is defined and what happens to items outside that scope. The same page lists exclusions, including event and email history, reporting data and a contact's specific position within an automation.

That exclusion changes the cutover plan. If a person was midway through a workflow in the source system, the team must decide where that person should enter in the destination rather than assume progress will be copied. The vendor also advertises onboarding for eligible plans, with support varying by plan. Even when a service is included, internal hours, tests and any external assistance belong in the budget.

Step 3: How can a team verify that migration worked?

Migration works when the relevant data and rules reach the destination and tests confirm the expected behavior. Completion alone proves little. The owner compares source and destination, investigates discrepancies and releases each workflow only after acceptance; an import by itself does not prove that campaigns and integrations are correct.

Start with counts by status and a sample of fields, tags and suppression records. Totals can match while an essential classification ends up in the wrong place. Record each discrepancy, its cause and the correction decision before using the contact base for a campaign.

Before sending campaigns, confirm that previous unsubscribes and other communication restrictions were preserved in the destination. Test unsubscribe links and confirm that new requests update the applicable lists. For each critical automation, check its trigger, actions, exit conditions and updates to connected systems. ActiveCampaign's post-migration review recommends checking those elements before activation.

Acceptance needs an owner. Marketing validates segments and communication; the integration owner validates data exchange between systems; procurement checks the ending or overlap of contracts. The time to enter production depends on scope and tests, not on a date established by the public pricing table.

How should a team fix common migration failures?

Start with the data. If counts or statuses differ, identify the source field, compare counting and classification criteria, and correct the mapping before releasing a campaign. Stop sending if unsubscribe handling fails. Test that rule again, and if a trigger fails, review its conditions and repeat the test with its owner.

A matching total is not enough when the wrong contacts are eligible for communication. Reconcile the status and the field used by the segment as well as the count, then document the correction and obtain acceptance before the next send.

What changes ActiveCampaign's total cost in Brazil?

Total cost combines the subscription, add-ons and migration for the same period and use. Direct purchase requires confirmation of the actual billing currency; if billed in dollars, use the effective exchange rate and validate applicable charges with finance. Local proposals need itemized prices, tax documents, services and limits before a decision.

Do not assume savings.

Direct TCO in Brazilian reais = subscription and add-ons in the actual billing currency, converted to reais when necessary + applicable buyer charges validated by finance + migration, integration, operating and contract-overlap costs.

Local proposal TCO in Brazilian reais = proposal price + add-ons, overages and services not included + internal migration and operating costs.

Compare the same period, contact tier, users, sends, automations, integrations and support level. Separate recurring expenses from one-time costs. The software subscription total-cost method helps organize expenses that do not appear on a plan's price label.

For direct purchase, the exchange rate applied and the tax burden of any remittance remain unknown until finance and the company's specialists review them. The ActiveCampaign catalog on Nexforce Marketplace states that contracting in Brazilian reais with a Brazilian tax invoice is available, but the price for the CNPJ, timing, scope and document applicable to the transaction must be confirmed in the proposal. There is no basis to promise savings, automatic tax credit or a fixed price throughout the contract.

Ask the proposal to identify the price-adjustment currency, renewal, overages and who performs implementation. The guide to software purchase order control addresses how teams divide those responsibilities. A proposal can be more convenient for finance and still require a price and scope comparison.

Which plans fit different B2B operations?

Starter is the first candidate for a small team whose workflows stay within its limits. Evaluate Plus or Pro when required channels, actions, features or access do not fit Starter. Enterprise is the public table's choice for SSO, while additional governance requirements such as SCIM and data residency need their own confirmation before procurement treats them as covered.

Do not upgrade in advance. A team with one user and short automations should test Starter against its inventory, including projected contacts and sends. Plus adds channels and removes the five-action limit per automation, but still includes one user in the 1,000-contact selection.

Pro includes three users and adds attribution features for the team to evaluate against a documented task. Enterprise SSO addresses an identified access requirement, but it does not prove that SCIM or a particular storage region is available. Request evidence for each control before putting the security list into a contract.

What should the team review after 90 days of operation?

After 90 days, the team should compare actual usage with contracted limits and review automation quality. Look for contacts without a classification, sends approaching the allowance and integrations without an owner. This is a management recommendation, not a reported test result, and any plan change should answer an observed need.

The administrator compares contacts by status with the contracted tier and reviews the trend in direct and automated sends. The same review records AI credit consumption and checks whether a scheduled task or advanced action was affected. Upgrade only for an observed limit or a new requirement.

Review the most important automations. For each one, confirm the owner, source of fields, entry and exit conditions, and most recent change. When a commercial process changes, an old tag can keep a contact in the wrong segment without producing a technical error.

Record support responses to tickets actually opened and the team's experience maintaining integrations. The software renewal governance guide complements that review: before renewal, procurement needs to know what was used, which limit would justify a change and which conditions the proposal sets for the next term.

Frequently asked questions

Four answers close the comparison: the price for the actual contact base, the billing currency and tax invoice, the scope of migration, and the renewal terms proposed for the buyer. The table is a reference. The proposal and the finance review must settle the conditions that public pricing does not demonstrate for the buyer's particular contract.

What is the price for the actual contact base?

Request the tier for all contacts that count toward the account, the monthly send volume, the plan and the number of users required. Confirm the billing period and add-on costs. Prices for 1,000 contacts do not replace that proposal.

Can a company contract in Brazilian reais with a tax invoice for its CNPJ?

The catalog states that contracting in Brazilian reais with a Brazilian tax invoice is available. The buyer should confirm the amount for its CNPJ, the price-adjustment currency and the applicable tax document in the proposal. ActiveCampaign's currency selector alone does not answer those questions.

What is included in migration?

The onboarding page mentions up to 10 free objects for eligible plans, but the company needs to confirm eligibility, the definition of objects and exclusions. Request the test scope. Ask who owns each integration and the terms for additional work. Internal hours remain. That is true even when the vendor's service is included.

How do renewal, cancellation and add-ons work?

The proposal should state the contract period, renewal, cancellation, extra-user pricing and overage terms. The public page review did not establish those terms or confirm them for a specific Brazilian contract. Finance and the contract owner should review them before signing.

References and further reading

Check the source dates. ActiveCampaign's pricing page and onboarding page provide the plan and migration information used in this guide; buyers should verify any changes against their own account and proposal.

References and where to request a proposal

The prices and limits in this guide were checked on November 11, 2026, on ActiveCampaign's official page with 1,000 contacts, USD and annual billing selected. Use the inventory as the basis for the decision, and request a proposal covering the same plan, volumes and required migration.

Check the scope first.

The official plans page and migration documentation allow buyers to check subsequent changes. On the ActiveCampaign page in Nexforce Marketplace, a buyer can request terms for its CNPJ. The inventory also supports proposal comparison: if one proposal covers fewer assets than another, the price difference does not establish savings, because the buyer still needs to fund the omitted work. Compare the same scope.

What is the buyer's next step?

The next step is to measure the operation before negotiating. Count the contacts who receive campaigns, the monthly send volume, the users who create automations and the active integrations, because each number changes the pricing tier and migration scope. Without those figures, the proposal answers the public pricing table. It does not answer the needs of the buyer's contact base.

Take those figures to the ActiveCampaign page in Nexforce Marketplace and request terms for the company's CNPJ. The comparison is complete only when price, currency, tax document and migration scope are in the same document.