Migrate from Tubular CRM to Salesforce Sales Cloud

Tubular Contacts map to Salesforce Lead for unqualified or prospect-status records and to Salesforce Contact for qualified or customer-status records. We define the split rule during scoping based on the customer's Tubular pipeline and status definitions, compute the split at migration time, and preserve the original Tubular contact status in a custom field tubular_original_status__c on both Lead and Contact for audit. The Contact-Account relationship resolves by matching the Tubular Contact's associated company name to a Salesforce Account record created from the Tubular Company extract.

Tubular Company records map directly to Salesforce Account. The company name becomes the Account Name field and is used as a dedupe key during import. Account is created before any Contact import so that the AccountId Lookup is satisfied at the moment of Contact insert. Companies with no associated Contacts are imported as Accounts without contacts to preserve the organizational record.

Tubular Deal records map to Salesforce Opportunity. The deal value maps to Amount, the deal name to Opportunity Name, and the pipeline stage assignment maps to the StageName tied to the appropriate Record Type and Sales Process that we configure in Salesforce before migration. We preserve closed-won and closed-lost dates as CloseDate and Custom Lost Date fields where applicable.

Each Tubular pipeline stage becomes a Salesforce Stage value in a Sales Process configured for the migration. Stage probability percentages migrate from Tubular to Salesforce StageProbability, rounded to the nearest integer. The Sales Process is assigned to a Record Type that we create per Tubular pipeline so stage values remain scoped per line of business.

Tubular Lead records map directly to Salesforce Lead. Lead source, status, owner, and any Lead Builder custom fields migrate to the Salesforce Lead equivalent fields. Tubular's lead-to-contact conversion logic does not exist in Salesforce and requires the customer's admin to run the standard Salesforce Lead Convert action post-migration.

Tubular Tags applied to Deals and Contacts migrate as a Salesforce custom multi-select picklist field named tubular_tags__c on both Opportunity and Contact. Multi-select picklists in Salesforce are limited to 255 characters and 500 values per field, so Tags exceeding this threshold are documented and reassessed with the customer during scoping. Tags used for categorization in Tubular are preserved as distinct values for segmentation in Salesforce reports.

Tubular Tasks associated with Deals and Leads map to Salesforce Task records. Task title, due date, owner (resolved via email to Salesforce User), completion status, and priority migrate directly. Recurring task patterns are not supported in Tubular export and must be documented for manual rebuild in Salesforce.

Tubular email logs, call logs, and meeting logs attached to Deals and Contacts migrate to Salesforce Task (for emails and calls with TaskSubtype set appropriately) and Event (for meetings). We use the Salesforce Bulk API 2.0 with batch chunking and parent-record lookup resolution on WhoId and WhatId. ActivityDate is set to the original Tubular timestamp to preserve timeline ordering. For Pro-tier customers with no API access, activity extraction depends on what the UI exposes in the CSV or manual export.

Tubular Users and Deal Owners map to Salesforce User records resolved by email match. Inactive users are flagged and the customer decides whether to provision inactive Salesforce Users for record reassignment or reassign records to active owners before migration. Owners without a matching Salesforce User are held in a reconciliation queue until the customer's admin provisions the account.

Tubular Enterprise Deal Stage Triggers are platform-native automation that fires email templates or workflow actions on deal stage changes. These do not exist in Salesforce and cannot be migrated as logic. We document each active trigger during discovery with its name, stage trigger condition, actions, and email template reference, and the customer's admin rebuilds equivalents in Salesforce Flow post-migration.

Tubular Email Templates are Enterprise-tier assets tied to Deal Stage Triggers. They do not migrate directly because Salesforce Email Templates use a different data model (HTML with merge fields tied to Salesforce fields). We extract the template body, subject, and merge field references during discovery and hand them to the customer's admin as a rebuild guide for Salesforce Email Templates or Lightning Email Templates.

PDFs and documents attached within deal flows in Tubular can be extracted via UI scraping or API where available. We preserve file names, creation dates, and the associated Deal reference, and migrate them as Salesforce ContentDocument records linked via ContentDocumentLink to the corresponding Opportunity. We do not host the files themselves; the customer provides access to the Tubular instance or the files are extracted from the UI.

Tubular reports including MoM/QoQ reports, Lead Source Reports, and Task Reports are view-only and have no export endpoint. We cannot migrate the historical data points embedded in Tubular reports. We advise the customer to screenshot or manually export any critical historical reports before migration cutoff. Post-migration, we recreate the report logic in Salesforce using standard report types and custom report types where needed, but the historical data points from Tubular are not importable.

Tubular DNA Credits power AI-enriched lead ratings and company profiles on the Enterprise tier. These credits do not transfer to Salesforce. We extract any AI-scored lead ratings and enriched company profile fields before migration cutoff and store them in Salesforce custom fields so enrichment context is not lost. Any enrichment features consumed after migration cutoff are lost.

If Tubular has custom objects or extended custom fields beyond the standard set, we migrate them to Salesforce custom objects with __c API naming conventions. We pre-create the destination schema in Salesforce including all custom fields, field types, lookup relationships, and any validation rules before data import begins. Custom object migration is scoped separately because it depends on the specific fields and relationships present in the source instance.