Migrate from Basic Online CRM to Salesforce Sales Cloud

Basic Online CRM Contacts map to Salesforce Lead as the primary target object. The platform has no concept of unqualified versus qualified prospects, so all Contacts land as Leads without a split. We map name, email, phone, and address fields 1:1. Any non-standard fields migrate as custom Lead fields with string type pending customer confirmation of intended data type. OwnerId is set from the customer-specified owner during write-back since Basic Online CRM does not surface record-level owner assignment.

Basic Online CRM Company records map to Salesforce Account. The company name becomes the Account Name field used as the dedupe key. Companies are a flat list in Basic Online CRM without subsidiaries or hierarchies, so no parent-account resolution is required. We flag duplicate company names appearing multiple times as Account duplicates for customer review before final import.

Basic Online CRM Deals map to Salesforce Opportunity. The critical complexity is the Deal-to-Contact association: Basic Online CRM references contacts by an internal numeric ID in its CSV export, not by name or email. We cross-reference these IDs against the exported contact list during the mapping phase, resolve each to a Lead name, and write the Opportunity with the resolved LeadId and AccountId. Any Deal referencing a deleted Contact is flagged as an orphaned Opportunity for customer resolution before cutover.

Basic Online CRM's pipeline stages migrate to Salesforce Opportunity Stage values. We pre-create a Sales Process in the destination org that matches the source stage count and names. Stage probabilities are mapped from Basic Online CRM if present, otherwise set to Salesforce defaults. If the source has more than 10 stages, we consolidate into Salesforce's 10-stage maximum per Sales Process.

Basic Online CRM Notes are free-text and untyped. We migrate them as Salesforce Note records linked via ContentDocumentLink to the parent Lead or Account. Any timestamps embedded in note text are not separable from content, so the Salesforce Note CreatedDate reflects the migration date rather than the original note creation date. Customers requiring original note timestamps should flag this during scoping for a custom timestamp extraction approach.

Basic Online CRM task records, if present, are simple title-and-status items with no due-date enforcement or assignee fields. We migrate them as Salesforce Task records with the task title as Subject and Status mapped to the equivalent Salesforce TaskStatus value. Assignee fields are set to the customer-specified default owner since Basic Online CRM does not expose assignee data in exports.

Basic Online CRM custom fields exist but are stored and exported as plain strings regardless of intended type. Date fields in particular may appear inconsistently across exports (e.g., "Jan 15 2024" in one export and "15/01/2024" in another). We standardise these during the transform phase but ask customers to validate custom field mappings before final import to confirm intended data types. All custom fields are pre-created in the destination Salesforce org as text fields first, then re-typed after customer sign-off on the mapping document.

Basic Online CRM does not host or store file attachments natively. Any documents referenced in Notes or Deal descriptions must be sourced externally and re-uploaded after migration. We include a pre-migration checklist item asking customers to identify and inventory any such files so that the re-upload plan is documented before cutover.

Basic Online CRM has a user concept but no explicit record-level owner assignment in its exports. We ask customers upfront which team member should own migrated records in the destination CRM and apply bulk OwnerId assignment during write-back. If the customer has multiple Salesforce Users and needs role-based ownership, we collect a mapping table during scoping.

Basic Online CRM's CSV export silently truncates at approximately 5,000 rows per download. We detect record counts during scoping and split large exports into multiple CSV files, merging them in the correct sort order before writing to Salesforce. For migrations above 5,000 Contacts, we coordinate with the customer to run sequential exports and provide the file list to FlitStack AI for reassembly before import.

Basic Online CRM Companies are a flat list with no hierarchy enforcement. Where the same company name appears multiple times, we flag these as potential duplicates and present them to the customer for resolution before final import. We do not auto-merge duplicates to avoid accidentally merging unrelated companies with matching names.

Any Deal in Basic Online CRM that references a Contact ID not present in the exported contact list is flagged as an orphaned Deal. We deliver a list of these records with the Deal name, associated company (if resolvable), and the unresolved contact ID. The customer decides whether to create placeholder Contacts, discard the Deals, or resolve manually before migration resumes.