1300 Australia is Telstra’s official Phone Word partner and CallN provides Cloud based Call Recording and Analytics
1300 Australia and CallN were using two different Salesforce organizations named 1300 Australia and CallN respectively, to manage CRM functionalities.
KloudSys was engaged to migrate CallN org into 1300 Australia org within a very short time period.
KloudSys proposed a well-defined plan and followed the plan persistently successful migrate by deadline.
To import records from one organization into another, you’ll need to import the records in a particular order to establish their relationships to one another. Record relationships are stored in Salesforce or defined by their IDs so you’ll need to populate your import files with any newly created record’s Salesforce Ids from the target org. The easiest way to do this is using Excel’s VLOOKUP function to add the new record Ids to your files for import. Recommended sample order for importing core objects:
If a vlookup isn’t something you’re comfortable with, consider creating a custom External Id field and map or insert your previous record Ids or other unique identifiers from your source organization into the field.
This will allow you to Import related records using an External ID. For example, after importing Accounts in your new org, you’ll replace any occurrences of legacy Account Ids in your import files with NEW Account Ids from the target org. To populate your import files with the newly created Account Ids use vlookup as outlined in the Add Salesforce IDs of existing records to your import file article.
