Portmux is a Zoho CRM to Salesforce migration service that moves your Leads, Accounts, Contacts, Deals, custom modules, and Blueprint workflows into Salesforce with the territory rules and approval processes your sales ops team designed.
Zoho-to-Salesforce is usually a scale move, growing teams hitting the limits of Zoho's customization and reporting. The two products share most CRM concepts (Leads, Accounts, Contacts, Deals), but Zoho's Blueprints, custom modules, and territory rules don't have direct Salesforce equivalents. We map each one explicitly.
Zoho Leads migrated to Salesforce Leads with Lead Source, Lead Status, custom fields, and Lead Assignment Rules re-implemented.
Zoho Accounts mapped to Salesforce Accounts with parent/child Account hierarchies and custom fields preserved.
Zoho Contacts migrated to Salesforce Contacts with Account association, custom fields, and Contact Roles on Deals carried forward.
Zoho Deals mapped to Salesforce Opportunities with Stage, Probability, Close Date, Forecast Category, and stage history.
Zoho custom modules (e.g. Projects, Subscriptions) recreated as Salesforce custom objects with all fields, lookups, and master-detail relationships.
Zoho Tasks, Calls, Meetings, and Events migrated to Salesforce Tasks and Events with original timestamps and Owner assignment.
Notes migrated as Salesforce ContentNotes; attachments migrated as Files associated to the parent record.
Zoho Blueprint state machines (e.g. Deal Approval, Onboarding) re-implemented as Salesforce Approval Processes or Flow Builder flows with the same transitions.
Zoho Workflow Rules and Macros mapped to Salesforce Flow, Process Builder, or Approval Processes depending on trigger type.
Zoho Territory Management rules re-implemented as Salesforce Enterprise Territory Management with territory hierarchy and assignment rules.
Zoho Email Templates ported to Salesforce Email Templates with merge field syntax converted from ${} to {!}.
Critical Zoho Reports rebuilt as Salesforce Reports; Zoho Dashboards rebuilt as Salesforce Dashboards.
We connect to Zoho CRM via OAuth with Admin scope, indexing every standard and custom module, custom field, Blueprint, Workflow Rule, and Territory definition. The Zoho CRM v6 REST API enumerates all data within 72 hours, and you see a complete module inventory plus a Blueprint translation proposal for each active state machine.
Mapping covers module-to-object, custom field translation, Blueprint to Approval Process or Flow, Territory rule conversion, and Workflow Rule re-implementation. Salesforce Sandbox is provisioned with the schema, and we load 10% of records as a test pass to validate field mapping before the full migration.
Salesforce Sandbox loaded with full Zoho history for UAT. Your sales ops team validates Blueprints, Approval Processes, and Reports against Zoho. On cutover day, Sandbox is promoted to Production, Zoho is set to read-only, and we run a final delta of post-cutover Zoho activity (typically <100 records).
Every migration has its own gotchas. Here's what we plan for on this specific path.
Zoho Blueprints are state machines with transitions, validations, and required fields per state. Salesforce uses Approval Processes (for approvals) and Flow Builder (for state-driven processes). Each Blueprint gets a tailored translation, simple Blueprints become Approval Processes; complex multi-branch Blueprints become Flows.
Zoho custom modules can have many-to-many relationships via custom-built junction modules. Salesforce uses junction objects with master-detail relationships. We recreate the junction structure with Salesforce master-detail rules, which can change cascade-delete behavior, we document each behavior change for sign-off.
Zoho Territory rules and Salesforce Enterprise Territory Management have different topology (Zoho is rule-based; Salesforce is hierarchical with assignment rules). We design the Salesforce territory hierarchy from your Zoho rules, then validate that the same accounts land with the same reps before cutover.
Zoho uses Profiles and Roles for access control. Salesforce uses Profiles + Permission Sets + Sharing Rules + Roles. We don't 1:1 translate; we design Salesforce security from your effective Zoho permissions per user, then re-provision users in the cleaner Salesforce model. Often results in fewer Profiles than the source had.
Single-system migrations like Zoho CRM to Salesforce run as Track A engagements: one source, one destination, up to 1M records, 4–6 weeks. Final price depends on object volume, custom field count, and integrations, scoped on a 20-minute call before any commitment. See full pricing →
Tell us what's in the source, where it's going, SaaS or custom, and when you need to be live. You'll walk away with a scoped quote, a named engineer, and a go-live date.