Migrate data to Skedulo
NoteThe below information applies to Skedulo Pulse Platform customers. If you are a Skedulo for Salesforce customer please leverage salesforce data migration tools and best practices.
You can migrate data by importing or inserting records from a legacy system of record into a new target environment. It’s important to import object data in a particular order to maintain record relationships. It’s necessary to configure your environment and add users in your new or target environment before beginning.
Record relationships are defined with Unique Identifiers (UID’s) in Skedulo, not record names. You will need to match and replace old record IDs in your import files with the newly created data’s record IDs from within your target environment to properly prepare relational data for import.
Before you start
Support is available for specific or directed questions or concerns that may arise during your migration however, consultation for overall scoping, planning, and implementation or execution of data migrations and required data manipulation is not within the scope of Support.
Migration planning and testing must be carried out client-side by customers. If you feel this task may be too much or aren’t confident with your organization’s ability to manage or complete the migration of configuration and data, you may elect to contact your Customer Success Manager or Account Executive to discuss Professional Services. Please note, there will be a cost involved if professional services or a consulting partner is tasked with completing the data migration on your behalf.
Migrate your data
There are different approaches and tools to support you in migrating your data to Skedulo.
|Tool||Description||Capabilities||Internal or external to Skedulo|
|Onboarding Wizard||An in-browser wizard that imports Users, Regions, Resources, and Job Types.||Import and update||Internal|
|Data Loader||A cloud-based data management tool that supports importing data into all standard and custom objects.||Import, update, and delete||Internal|
|API||A graphQL based API supporting the programmatic mutation and extraction of records.||Import, update, delete, and export||Internal|
|ETL||A third-party tool such as Informatica, Dell Boomi, Talend that can be configured to automate Extracting, Transforming, and Loading data from one system to another. Note: Additional subscriptions to these products may be required in addition to services costs to configure them for your specific data migration project.||Import, update, delete, and export||External|
To import records from one system into Skedulo, you’ll need to import the records in a particular order to establish their relationships to one another. Record relationships are stored in Skedulo and are defined by their IDs so you’ll need to populate your import files with any newly created record’s Skedulo UIDs from the target environment. The easiest way to do this is using Excel’s VLOOKUP function to add the new record UIDs to your files for import.
For example, after importing Accounts in your new environment, you’ll replace any occurrences of legacy Account UIDs in your import files with the NEW Account UIDs from the target environment. To populate your import files with the newly created Account UIDs use vlookup as outlined above.
How objects relate to one another can be graphically viewed using the Documentation Explorer in GraphiQL (an in-browser GraphQL IDE) to assist in devising a strategy and planning your object’s appropriate import order.
You need to define and include the UID of related records during import by replacing occurrences of old legacy record UIDs with new related record Ids from the target Environment within your import file. This ensures that each of the new records is properly associated with one another.
Was this page helpful?