CRM migration
Field-level mapping, validation, and rollback between webCRM and Salesforce Sales Cloud. We move data and schema; workflows are rebuilt natively in Salesforce Sales Cloud.
webCRM
Source
Salesforce Sales Cloud
Destination
Compatibility
7 of 12
objects map 1:1 between webCRM and Salesforce Sales Cloud.
Complexity
CModerate
Timeline
4-6 weeks
Overview
Moving from webCRM to Salesforce Sales Cloud requires navigating a platform with no public API on the source side and a fully REST- and Bulk-API-driven destination. webCRM exports data through its Utilities > Overviews menu as manual CSV or via the Zynk connector in webCRM Delivery XML format, which must be flattened and restructured before loading into Salesforce. We guide customers through the Overviews export process, parse the nested XML for Deliveries and line items, and load all objects through Salesforce's Bulk API 2.0 with batch chunking and parent-record lookup resolution. webCRM automation rules are not accessible via export and cannot migrate; we deliver a written inventory of every active automation for the customer's admin to rebuild in Salesforce Flow. Custom fields on Organisations, Contacts, Deals, and Products map individually to typed Salesforce custom fields, and we flag any Organisation-specific fields that require Salesforce custom object creation if the field model is unique to webCRM.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a webCRM object lands in Salesforce Sales Cloud, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
webCRM
Organisation
Salesforce Sales Cloud
Account
1:1webCRM Organisations map directly to Salesforce Account. Organisation name becomes Account Name; industry, website, and address fields map by label match. webCRM custom fields on Organisation require mapping to Salesforce custom fields on Account, and any Organisation-specific taxonomy (e.g., regional codes or internal segmentation flags) is preserved as a custom picklist or text field. Account is created first so that the AccountId reference is available for Contact inserts in the next phase.
webCRM
Contact
Salesforce Sales Cloud
Contact
1:1webCRM Contacts map to Salesforce Contact. Each Contact's Organisation ID is resolved to the Salesforce AccountId during import, maintaining the parent-child relationship. webCRM contact custom fields (e.g., department, role, secondary phone) map individually to Salesforce Contact custom fields. If a Contact has no matching Organisation in webCRM, it creates an Account on the fly during import.
webCRM
Deal
Salesforce Sales Cloud
Opportunity
1:1webCRM Deals map to Salesforce Opportunity with AccountId and ContactId lookups resolved at migration time. The webCRM deal stage name maps to a Salesforce StageName value, and we configure the corresponding Sales Process in Salesforce before migration so that only valid stage transitions are available. Deal amount, close date, and probability transfer directly; any custom deal fields map to Opportunity custom fields.
webCRM
Delivery
Salesforce Sales Cloud
Order and OrderProduct
1:manywebCRM Deliveries export in webCRM Delivery XML format via the Zynk connector. The nested XML structure (Delivery header with embedded line items) is parsed and flattened into two Salesforce object types: Order (the delivery header with delivery date, delivery address, and delivery status) and OrderProduct (one row per line item with product reference, quantity, and unit price). The parent Organisation is resolved to AccountId, and any Contact reference on the Delivery becomes the Order's AccountContactId.
webCRM
Product Database
Salesforce Sales Cloud
Product2 and PricebookEntry
1:1webCRM Products map to Salesforce Product2 records with Standard Price Book entries. Product name, SKU (hs_sku equivalent), description, and list price transfer. We create PricebookEntry records for the Standard Price Book during import so that Products are immediately available for quoting or order management. If webCRM maintains inventory quantities, we create a custom field on Product2 to store the migrated value.
webCRM
Task
Salesforce Sales Cloud
Task
1:1webCRM Tasks linked to Organisations or Contacts map to Salesforce Task. The original webCRM task status (e.g., Open, Completed, Overdue) maps to Salesforce Task Status with a custom mapping table since label conventions differ between platforms. Task due date, subject, and description transfer directly. Tasks linked to Deals map with the WhatId pointing to the Salesforce Opportunity record.
webCRM
Custom Field (Organisation)
Salesforce Sales Cloud
Custom Field (Account)
lossyWe extract the full webCRM custom field schema for Organisations during scoping. Each webCRM custom field is assessed for Salesforce field type (text, number, picklist, date, checkbox) and created on Account before the Account import phase. webCRM Organisation-specific fields that have no Salesforce standard equivalent require a Salesforce custom field, and we note this in the mapping document for customer sign-off.
webCRM
Custom Field (Contact)
Salesforce Sales Cloud
Custom Field (Contact)
lossywebCRM Contact custom fields are extracted during scoping and mapped to Salesforce Contact custom fields with equivalent types. Multi-select or tag-style fields in webCRM migrate to Salesforce multi-select picklist. Any Contact fields referencing lookup relationships in webCRM (e.g., reporting_to another Contact) are resolved to the Salesforce Contact ID at migration time.
webCRM
Custom Field (Deal)
Salesforce Sales Cloud
Custom Field (Opportunity)
lossyDeal-level custom fields in webCRM migrate to Opportunity custom fields. Picklist values specific to webCRM (e.g., deal source channel or regional classification) are mapped to Salesforce picklists with the same values, or to a custom field if the value set exceeds Salesforce's 500-value picklist limit.
webCRM
Custom Field (Product)
Salesforce Sales Cloud
Custom Field (Product2)
lossywebCRM Product database custom fields (e.g., internal cost, supplier code, unit of measure) map to Product2 custom fields. These are created before the Product2 import phase so that the fields are available for population during data load.
webCRM
Owner
Salesforce Sales Cloud
User
1:1webCRM Owner references on Organisations, Contacts, Deals, and Tasks are resolved by email match against the Salesforce destination org's User table. We flag any Owner without a matching Salesforce User and hold those records in a reconciliation queue. The customer's Salesforce admin provisions missing Users before record import resumes.
webCRM
Note
Salesforce Sales Cloud
Note and ContentDocumentLink
1:1webCRM notes attached to Organisations, Contacts, or Deals migrate to Salesforce Note records linked via ContentDocumentLink to the parent Account, Contact, or Opportunity. Note body transfers as plain text or rich text depending on the original format, and any file attachments become separate ContentDocument records.
| webCRM | Salesforce Sales Cloud | Compatibility | |
|---|---|---|---|
| Organisation | Account1:1 | Fully supported | |
| Contact | Contact1:1 | Fully supported | |
| Deal | Opportunity1:1 | Fully supported | |
| Delivery | Order and OrderProduct1:many | Fully supported | |
| Product Database | Product2 and PricebookEntry1:1 | Fully supported | |
| Task | Task1:1 | Fully supported | |
| Custom Field (Organisation) | Custom Field (Account)lossy | Fully supported | |
| Custom Field (Contact) | Custom Field (Contact)lossy | Fully supported | |
| Custom Field (Deal) | Custom Field (Opportunity)lossy | Fully supported | |
| Custom Field (Product) | Custom Field (Product2)lossy | Fully supported | |
| Owner | User1:1 | Fully supported | |
| Note | Note and ContentDocumentLink1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
webCRM gotchas
Automation rules are not exported or migratable
Export requires manual Overviews navigation
Delivery XML format requires transformation
Salesforce Sales Cloud gotchas
Workflow Rules and Process Builder are retired
Bulk API batch quota exhaustion during large imports
Storage overage billing is non-obvious
Account-Contact many-to-many relationship mapping
Territory and team member import ordering dependencies
Pair-specific challenges
Migration approach
Discovery and Overviews export planning
We audit the webCRM portal for object volume (Organisations, Contacts, Deals, Deliveries, Products, Tasks), active automation rules, custom field schemas on each object, and any parent-child relationship data. We then provide a written Overviews export guide that walks the customer's webCRM admin through the Utilities > Overviews menu for each object type, specifies the columns to include, and instructs on file naming conventions. The exports are returned to us as CSVs or as Zynk-delivered XML for the Delivery object. This phase also includes a Salesforce edition decision: Professional ($80/user) covers most migrations; Enterprise ($165/user) is required for record-triggered Flow at scale or advanced territory management.
Schema design and custom field provisioning
We design the destination Salesforce schema based on the webCRM custom field inventory. For each webCRM custom field, we create the equivalent Salesforce custom field with the appropriate type (Text, Number, Picklist, Date, Checkbox, Long Text Area) on the corresponding object (Account, Contact, Opportunity, Product2). We configure Sales Processes and Record Types for the Opportunity object that correspond to the webCRM deal stages. All schema is deployed to a Salesforce Sandbox via metadata API for validation before production migration begins.
Delivery XML transformation and staging
webCRM Deliveries exported via Zynk in webCRM Delivery XML format are staged in a transformation environment. We parse the nested XML, split the header element into an Orders staging dataset, and extract line items into an Order Products staging dataset. Organisation references are resolved to AccountIds, and product references are matched against the Product2 staging table. Any XML records with malformed elements or missing required fields are logged with row numbers for customer review and correction before load.
Sandbox migration and reconciliation
We run a full migration into a Salesforce Sandbox (Full Copy or Partial Copy) using production-equivalent data volume. The customer's RevOps lead reviews record counts across all objects, spot-checks 25-50 records per object against the webCRM source, and validates that Account-to-Contact relationships, Opportunity-to-Account relationships, and Order-to-Account relationships are intact. Any mapping corrections are applied to the production migration plan before cutover.
Production migration in dependency order
We execute production migration in record-dependency order: Accounts (from webCRM Organisations), Contacts (with AccountId resolved), Opportunities (with AccountId, OwnerId, and RecordTypeId resolved), Product2 and PricebookEntries (from webCRM Product Database), Orders and Order Products (from transformed Delivery XML), Tasks (with WhatId resolved to Opportunity where applicable), and Notes (linked via ContentDocumentLink). Owner resolution by email is validated before each phase. Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, validation, and automation rebuild handoff
We freeze webCRM writes during cutover, run a final delta migration of any records created or modified during the migration window, then enable Salesforce as the system of record. We deliver the webCRM automation inventory document to the customer's admin team with recommended Salesforce Flow equivalents for each rule. We support a one-week hypercare window for reconciliation issues. We do not rebuild webCRM automation rules as Salesforce Flow inside the migration scope; that is a separate engagement or an internal admin task.
Platform deep dives
webCRM
Source
Strengths
Weaknesses
Salesforce Sales Cloud
Destination
Strengths
Weaknesses
Complexity grading
Moderate CRM migration. 4 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Moderate migration
Derived from compatibility, mapping clarity, API constraints, and data volume across webCRM and Salesforce Sales Cloud.
Object compatibility
4 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
webCRM: Not publicly documented.
Data volume sensitivity
webCRM doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during webCRM to Salesforce Sales Cloud migration scoping. Not seeing yours? Book a call.
Walk through your webCRM to Salesforce Sales Cloud migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave webCRM
Other ways to arrive at Salesforce Sales Cloud
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.